sprrint_sprints_delete

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

With no annotations, the description discloses the destructive nature ('Delete') and a concrete consequence: move=free sends remaining tasks to the Black Hole. It does not state irreversibility or other move values, but the core behavior is transparent.

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 short sentences with the primary action first and a valuable behavioral detail second. No filler or redundant phrasing.

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?

The description is too minimal for a destructive operation with no annotations and no output schema. It omits return expectations, whether deletion is permanent, how project scopes the sprint, and behavior when move is not free.

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 0% and the description only explains move=free. The required slug parameter and optional project parameter are left undocumented by both schema and description, so the agent must infer their meaning from names.

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 states a precise action: 'Delete a sprint.' It identifies the resource (sprint) and verb (delete), and the Black Hole detail further distinguishes this tool from generic delete or update tools.

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?

There is no guidance on when to use this delete tool versus alternatives, no prerequisites, and no warnings about when deletion is inappropriate. The only usage hint is the obvious purpose embedded in the name and description.

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