delete_story

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

Description discloses permanence, irreversibility, guarded behavior (confirm flag), and intended use case. Annotations already indicate destructiveHint true, but description adds the critical detail about warning vs deletion, which is beyond annotations.

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 concise sentences, each adding value. Front-loaded with the core action and irreversibility. No unnecessary words.

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 output schema, the description adequately covers behavior, parameter effects, and return conditions (warning vs deletion). It is complete enough for correct invocation.

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%, so parameter descriptions in schema are sufficient. The description reinforces the confirm parameter's guarded behavior but does not add new meaning beyond the schema's description.

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 clearly states the action (delete), resource (Story), and input (issue key). It distinguishes from sibling tools like create_story, update_story, and get_story by specifying a destructive operation.

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 description provides clear context: irreversible, requires confirmation, intended for human-approved cleanup. It implicitly warns against casual or automated use but does not explicitly name alternatives like transition_story or update_story for deactivation.

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