ncloud_sourcecommit_list_branches

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

Annotations already declare readOnlyHint=true, so the description's 'list all branches' is consistent. It adds value by noting that the output includes default branch info, which is useful for understanding the response. No contradictions with annotations.

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?

The description is a single, concise sentence of 12 words that conveys all essential information. No superfluous text, perfectly front-loaded.

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 list operation with one required parameter and no output schema, the description is mostly complete. It explains what the tool does and highlights that default branch info is included. It could mention pagination or result limits, but these are minor omissions.

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?

Schema coverage is 100% for the single parameter 'repositoryName' with a clear description 'Name of the repository'. The tool description does not add any additional meaning or context to this parameter, so baseline 3 is appropriate.

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 tool's purpose: 'List all branches in a SourceCommit repository (includes default branch info)'. It specifies the verb 'list', the resource 'branches', and the scope 'all branches in a SourceCommit repository', distinguishing it from sibling tools like ncloud_sourcecommit_list_tags or 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?

The description does not provide any guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it point to other tools for related operations (e.g., setting a default branch). Given the large number of sibling tools, the lack of usage context is a shortcoming.

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