delete_tag

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

Beyond the destructiveHint annotation, the description discloses a non-obvious behavior: deletion is refused for release-referenced tags unless force is set, and it explains the consequence of removing such a tag. This is valuable, specific behavioral context that is not available from annotations alone.

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 two sentences with no filler. The main action is front-loaded, and the second sentence earns its place by explaining the critical force behavior and its rationale.

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 delete operation, the description covers the action, the special case where force is required, and the reasoning behind that behavior. With the destructiveHint annotation and an output schema present, nothing essential is missing for an agent to select and invoke this tool correctly.

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?

The description clarifies the force parameter by explaining when it is required, adding meaning beyond the schema. However, with only 25% schema description coverage, the three required parameters — repo_owner, repo_name, and tag_name — are not explicitly defined in the description. Their names are self-explanatory, but the description does not fully compensate for the low schema coverage.

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 opens with a specific verb and resource, "Deletes a tag," which directly states the tool's function. It also distinguishes this from release-oriented tools by explaining the tag-release relationship, making it easy to select over sibling tools like delete_release or create_tag.

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 clearly conveys the condition under which force is needed: deletion is refused when a release points at the tag. However, it does not explicitly mention when to prefer this tool over alternatives or when not to use it, so the usage guidance is mostly implied rather than stated.

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