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

Annotations already flag destructiveHint/readOnlyHint/idempotentHint, but the description adds what annotations cannot: the deletion does not scrub the label name from stories because story labels live as a string array. That is precisely the kind of hidden side effect an agent must know before deleting.

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, both load-bearing: the first states the action and its key limitation, the second routes to the follow-up tool. No filler or restated name.

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 this covers everything: what is deleted, what is NOT deleted, and how to do the remaining cleanup. No output schema is needed since deletion has no meaningful return to describe.

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 one parameter (labelId), fully documented in the schema as a UUID, so the description needs no compensation. It adds no extra parameter detail, but none is warranted for a single required 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?

States a concrete verb and resource ('Delete a Label row') and immediately scopes it: metadata only, not the story-side string array. That distinction separates it from the other delete_* siblings and from update_label.

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?

Explicitly names the alternative path for the adjacent task ('Use bulk_update_stories with labels.mode=remove to clean up story-side associations'), giving the agent a routing rule rather than leaving it to guess which tool handles story labels.

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