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

Annotations already flag destructiveHint=true, but the description goes further by disclosing cascade scope (removal from every post of the workspace), the non-destructive consequence for posts, and irreversibility. That is exactly the behavior an agent cannot derive from structured fields and it directly shapes safe invocation.

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?

Three short clauses, front-loaded with the action, then the blast radius, then the safety requirement. No filler sentences and nothing repeated from the title or annotations.

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 one-parameter destructive tool with full annotation coverage and no output schema, nothing an agent needs is missing: what it deletes, what survives, whether it is reversible, and the confirmation prerequisite are all present.

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% and the single 'id' parameter already documents that it comes from list_tags, so the description adds no parameter-level detail. A baseline 3 is appropriate since the schema fully carries this burden.

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?

States a specific verb and resource ('Delete a post tag') and immediately scopes the effect: the tag is removed from every post in the workspace while the posts themselves persist. That distinguishes it cleanly from update_tag and the delete_* siblings that remove other resource types.

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?

Usage is clearly implied by the destructive framing plus the explicit instruction to confirm with the user first, which functions as a prerequisite for invocation. It does not name an alternative such as update_tag for renaming, so the agent must infer that a rename is not the right path here.

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