git-remote-remove

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

With no annotations, the description carries full burden for behavioral disclosure. It only states that the tool removes a remote repository, but fails to disclose whether it is destructive, what happens to tracking branches, or whether it requires force. No side effects or failure conditions are mentioned.

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 sentence and front-loaded, but it is overly terse. While concise, it could include more context (e.g., 'from the git configuration') without significant bloat. It earns its place only by stating the core action.

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 simplicity (2 parameters, no output schema) but the presence of many siblings, the description is incomplete. It should clarify that removal is irreversible, only affects the local alias, and requires no special permissions. The current text leaves agents unsure about behavioral nuances.

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 both parameters already described. The description adds no additional meaning beyond the schema for 'name' and 'directory', so a baseline score of 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 'Removes a remote repository' uses a specific verb 'removes' and explicitly names the resource 'remote repository', clearly distinguishing it from siblings like git-remote-add, git-remote-list, and git-remove/git-remove-all which deal with local files.

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. It does not mention prerequisites (e.g., remote must exist), nor does it contrast with git-remote-add or git-remove-all.

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