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

Goes well beyond the annotations: sets deletedAt, exposes the nightly cleanup-cron hard-delete after 7 days, and documents the ALREADY_DELETED soft error on tombstoned rows. This is exactly the mutation lifecycle and error behavior an agent needs before calling a destructive 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?

Four short sentences, each contributing distinct information (soft semantics, grace window, undo path, error code), with the core behavior front-loaded.

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 tool with no output schema, the description covers lifecycle, reversibility, timing, and error semantics, leaving nothing material an agent needs unstated.

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 storyId description already explains the ticket-key/UUID formats, so the schema carries the load. The description adds only the tombstoned-row context, not parameter-level detail, so baseline 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?

States a specific verb and resource: 'Soft-delete a story.' This immediately distinguishes it from the other delete_* siblings and from restore_story, and the 'soft' qualifier gives the agent the key semantic difference from a hard delete.

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 stride.restore_story as the undo path and the 7-day grace window as the condition for it. It doesn't discuss when to prefer other delete variants, but for a delete tool the alternative that matters (undo) is covered.

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