Github Delete Tag

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

Besides the destructiveHint annotation, the description reveals a specific non-obvious behavior: deleting a tag that a release points at will be refused unless force=true, and it explains the rationale. This adds meaningful behavioral context beyond the annotation. It does not contradict the annotation and is honest about the deletion risk.

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?

Two sentences with no filler; the core action is front-loaded and the safety caveat follows. The slightly awkward second sentence does not hurt clarity or compactness.

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 simple destructive tag deletion with annotations marking it destructive and an output schema present, the description covers the key operational nuance (force requirement). Missing parameter explanations are the main gap, but self-evident names and schema reduce the need. Overall adequate for an agent to invoke it 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?

Only 1 of 4 parameters (force) has schema documentation, and the description partially re-explains it with the release-refusal semantics; it does not add descriptions for repo_owner, repo_name, or tag_name. The parameter names are intuitive, but with only 25% schema coverage the description bears more responsibility and does not fully compensate.

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 clear verb+object: 'Deletes a tag.' It further distinguishes itself from sibling delete tools such as github_delete_release and from github_create_tag by focusing on tags and explaining the release-point interaction. This is enough for an agent to identify what resource this tool acts on.

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 gives no guidance about when to select this tool over github_delete_release or github_create_tag. It states the force/refusal condition, which is operational context rather than tool-selection guidance. There are no explicit when-to-use or alternative references.

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