ncloud_sourcedeploy_get_sourcecommit_repos

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

Annotations include readOnlyHint=true, and the description's 'Get' is consistent. The description adds the useful context that the repos are 'available' for scenario configuration, implying some eligibility filtering. However, it doesn't disclose details like whether the list is paginated, what happens if no repos are available, or whether special permissions are needed beyond what annotations imply.

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?

A single sentence of 12 words that is direct and free of unnecessary jargon. It front-loads the action and resource, making it immediately scannable by an agent.

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 zero-parameter read-only tool with good annotations, this description is nearly complete. It names the resource and the context. However, it doesn't clarify what 'available' means (e.g., only repos the user can access or that are eligible for SourceDeploy), which would further aid an agent's expectations.

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?

The tool has zero parameters, so the baseline is 4. The description adds meaning by clarifying the result set is specifically the 'available' repositories for scenario source configuration, which helps the agent understand what the response represents without needing parameters.

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?

The description clearly states the verb 'Get' and the resource 'list of available SourceCommit repositories', adding the specific purpose 'for scenario source configuration'. This distinguishes it from the more general ncloud_sourcecommit_list_repos sibling by indicating this is the filtered/eligible list for SourceDeploy scenarios.

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?

The phrase 'for scenario source configuration' provides clear context for when to use this tool—when setting up a SourceDeploy scenario that needs a SourceCommit repository. It does not explicitly name alternatives, but the purpose is specific enough to guide selection among sibling tools.

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