ncloud_sourcedeploy_get_sourcecommit_repos

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true, and the description accurately describes a read operation ('Get the list'). No contradiction, but no additional behavioral context beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single 12-word sentence that directly conveys the tool's purpose without any extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple parameterless listing tool with readOnly annotations, the description is sufficient. However, it could be improved by explicitly stating the output format (e.g., 'returns a list of repository names').

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters in the schema, so description does not need to explain parameters. Schema coverage is 100% with an empty schema, and the description adds no param info but is consistent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly specifies the verb 'Get', the resource 'SourceCommit repositories', and the context 'for scenario source configuration'. This distinguishes it from sibling tools like ncloud_sourcedeploy_get_sourcecommit_branches and ncloud_sourcecommit_list_repos.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description states the purpose but does not provide guidance on when to use this tool versus alternative listing tools (e.g., ncloud_sourcecommit_list_repos). No explicit when-not or alternative mention.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.