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

The annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds important context beyond them: the removal affects every ticket, it is irreversible, and only owners may perform it. These are exactly the kind of behavioral and authorization details an agent needs before invoking a destructive mutation.

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 four short sentences and front-loads the core action before adding scope, reversibility, and permission details. There is no wasted text.

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 single-parameter destructive mutation with rich annotations and a fully described input schema, the description covers the critical context: what it does, its global effect, irreversibility, and owner-only access. No output schema exists, so return-value explanation is unnecessary.

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 has 100% description coverage and documents button_id as a uuid obtainable from list_buttons. The tool description adds no further parameter detail, so the schema already does the heavy lifting and the baseline score of 3 is appropriate.

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 and resource, "Remove a button," and immediately states the scope of the effect: "It disappears from every ticket." This clearly distinguishes it from sibling tools such as create_button, update_button, list_buttons, and press_button.

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?

"Owner only" gives a clear permission prerequisite, and "Irreversible" signals caution before use. However, it does not explicitly route agents to alternatives such as update_button for non-destructive changes or list_buttons for finding the button id.

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