delete_user_story

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

With no annotations, the description carries the full burden. It discloses that deletion cascades to all sub-tasks, that it validates completed work and external dependencies, and that force bypasses the completed-work guard. This is valuable behavioral insight beyond the schema. Minor gap: the exact behavior for external dependencies (block vs warn) is not specified.

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, front-loaded with the primary action, followed by necessary conditions. No redundancy, every clause adds unique information.

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 2-parameter deletion tool with no output schema, the description covers the core behavior, side effects (cascading delete), safety checks, and parameter override. It could mention the outcome for external dependencies, but overall it's sufficiently complete.

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?

Both parameters are already documented in the schema (100% coverage). The description adds meaning by explaining the force parameter's role in overriding completed-work checks, which the schema only describes as 'Force deletion even if there are completed sub-tasks'. It also contextualizes userStoryId as the parent story whose sub-tasks are deleted.

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 verb 'Delete' and the resource 'user story', and specifies cascading deletion of sub-tasks. It distinguishes itself from sibling tools like delete_task (which targets individual tasks) and safe_delete_tasks_by_status (which deletes tasks by status).

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 context about when to use force=true (with completed sub-tasks), implying standard usage without force. It also indicates the tool performs dependency checks, signaling caution. However, it doesn't explicitly mention alternatives for deleting individual tasks, but the related tool names provide that context.

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