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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation is a delete, implying destructive action, but it does not mention irreversibility, whether related data or versions are affected, authentication/authorization requirements, billing implications, or response behavior. This is a meaningful gap for a mutation tool.

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?

One short, front-loaded sentence that states exactly what the tool does with no filler. The description is appropriately sized for a simple delete operation, and every word earns its place.

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 destructive tool with no annotations, the description is too minimal. It omits important contextual details such as irreversibility, whether the design_id must come from roastify_list_designs (stated only in the schema, not the description), and any billing side effects. The presence of an output schema helps, but the description alone does not make the tool's usage fully transparent.

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 description contributes no parameter-level meaning beyond what the input schema already provides. The schema documents design_id and npub, but dpop_token remains unexplained, and the description does not clarify billing, ownership, or how the design is identified. The schema's own 'Required.' note on npub also conflicts with the actual required array, which is confusing.

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 a clear resource ('one of your stored designs'), distinguishing this tool from sibling delete tools like delete_coupon, delete_operator_credential, and delete_patron_credential. It is immediately clear what entity the tool acts on and that it operates on the caller's own stored designs.

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 phrase 'one of your stored designs' provides clear context that this tool is for removing designs owned by the user, not for other delete operations among the siblings. It does not explicitly enumerate when not to use it or mention alternatives, but the resource distinction is clear enough for selection.

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