Mooring

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

With no annotations provided, the description carries the full burden. It successfully discloses what data is returned (tracking info, ahead/behind counts), but lacks information about side effects, performance characteristics, or error conditions. The 'List' verb implies read-only behavior.

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 efficiently structured with the primary action upfront, followed by an Args section. The information is dense with minimal waste, though the 'Args:' formatting is slightly informal for an MCP description.

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?

Given the tool's low complexity (single parameter) and the existence of an output schema, the description is sufficiently complete. It appropriately previews the key output concepts (tracking info, ahead/behind) without needing to fully describe the schema structure.

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?

With 0% schema coverage (only 'title' present, no 'description'), the description compensates by documenting the repo_path parameter as 'Path to local git repository.' This provides necessary semantic meaning, though it could be richer (e.g., specifying absolute vs relative paths or validation requirements).

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 specific action ('List all branches') and distinguishes itself from siblings like repo_log, repo_diff, and repo_status by specifying the unique output content (tracking info, last commit, ahead/behind counts). The scope is precisely defined.

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 provides no guidance on when to use this tool versus alternatives (e.g., when to use repo_status instead) or any prerequisites. There is no 'when to use' or 'when not to use' information present.

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