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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing behavioral beyond that: it doesn't say whether deletion is permanent, whether it fails when the tag is in use on tasks, or what the response looks like. It essentially restates the annotation without enriching it.

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?

A single front-loaded sentence with the verb and resource first and no filler. It is appropriately sized for a simple two-parameter tool, though there is no additional structure because there is nothing extra to structure.

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 tool with an output schema absent but destructive/read-only hints present and full parameter documentation, the description is minimally sufficient. It omits any note about irreversibility or error behavior, which is acceptable but leaves the definition adequate rather than complete.

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 description coverage is 100%, so both parameters (name, projectKey) are fully documented in the schema and the baseline is 3. The description's phrase 'by name' and 'from a project' loosely maps to those parameters but adds no format, casing, or identifier details beyond the schema.

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 states a specific verb and resource ('Delete a tag') plus scope ('from a project by name'), so an agent can identify the operation immediately. However, it does nothing to distinguish this from siblings like create_tag, update_tag, or list_project_tags, which is where a 5 would require explicit differentiation.

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?

There is no when-to-use guidance, no mention of alternatives (e.g. update_tag for renaming), and no prerequisites such as permissions. The usage is only inferable from the verb itself, which is the definition of no explicit guidance.

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