git_remote

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

Beyond annotations (destructiveHint=true), the description details return formats ('one 'name -> url' line per remote', 'operation confirmation', 'No remotes configured.'), prerequisites ('add needs both name and url', 'remove/rename operate on existing remotes'), and explicitly states it does not transfer data. This significantly enriches behavioral context beyond the annotation flags.

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?

All sentences are information-dense and front-loaded with the primary purpose. The description is structured logically: purpose, use cases, return details, exclusions, and comparative advantage. No filler or repetition.

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?

Despite no output schema, the description fully explains return values and edge cases ('No remotes configured.'). It covers prerequisites, exclusions, and comparisons to alternative tools, making it complete for a moderate-complexity management tool.

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% with parameter descriptions, so baseline is 3. The description adds relationships between parameters (add needs both name and url; remove/rename operate on existing remotes), providing meaning beyond the individual schema fields.

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 'Manage remotes: list, add, remove or rename them', which is a specific verb+resource. It also distinguishes from siblings by explicitly contrasting with git_fetch, git_pull, and git_push, making its scope unambiguous.

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?

Provides explicit use cases ('where does this repo sync to?', 'configure a new upstream', 'fix a remote URL') and exclusions ('Does NOT transfer data') with named alternatives. This fully guides when to use the tool vs siblings.

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