git_tag

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

Beyond the destructiveHint annotation, the description adds important behavioral context: delete requires confirmed=True, annotated=True needs a message, and the return values differ by operation. This helps the agent understand side effects and prerequisites.

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 front-loaded with the core capability and then adds essential details. It is somewhat verbose with the 'Best for' line repeating earlier usage guidance, but every sentence adds useful information.

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 6 parameters and no output schema, the description covers all operations, key parameter constraints, and return value expectations. It does not explicitly describe repo_path, but that is adequately covered in the input schema.

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%, but the description adds relationships between parameters (e.g., 'delete requires confirmed=True', 'annotated=True needs a message') and clarifies expected outputs per operation, providing value beyond the schema definitions.

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 manages tags with a specific set of operations: list, create, delete. It explicitly differentiates from sibling tools by stating 'Does NOT branch or switch' and points to git_branch and git_checkout as alternatives.

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?

It provides explicit when-to-use guidance ('mark release points in history', 'list existing releases') and clear exclusions/alternatives: 'use git_branch for branches and git_checkout to switch to a tag'.

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