Delete Tag

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

With no annotations provided, the description carries full responsibility for behavioral disclosure, but it only states the action itself. It does not mention side effects, permissions, reversibility, cascading behavior, or what the output contains. The existence of an output schema is not leveraged in the text.

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 concise sentence with no wasted words. It is appropriately sized for a simple delete tool, though slightly under-specified for the project context, it remains efficiently front-loaded.

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 (one parameter, output schema present), the description meets the minimum viable threshold but adds little beyond the obvious. It does not clarify relationships with other entities (e.g., whether the tag is removed from issues), which a user might need to know in a project-management context.

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 schema already describes the tagId parameter with 100% coverage, so the baseline is 3. The description adds no additional meaning about the parameter, such as how to obtain the ID or whether it can be a name instead of an ID.

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 uses a specific verb ('Delete') and resource ('tag') with a scope ('from the project'), making it distinct from sibling delete tools that target comments, issues, sprints, or projects. It clearly states what the tool does.

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 implies usage for removing tags, but it does not explicitly state when to use this over alternatives or provide any exclusions. No context is given about when this should be invoked versus other tag-related tools like updateTag or addTagToIssue.

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