delete_sprint

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive profile is covered structurally. The description adds nothing beyond that: it does not say the deletion is irreversible, whether sprint issues are reassigned, or that the 'confirm' flag must be supplied for a destructive operation.

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?

A single, front-loaded sentence with no filler, which is appropriate for a simple delete. It is arguably under-specified rather than bloated, so it scores well on structure without being maximal.

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 mutation with no output schema and only partial parameter documentation, the description should cover confirmation requirements and side effects such as what happens to the sprint's issues. None of that is present, leaving the agent to guess at the blast radius.

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 only 50% — sprintId has no description at all. The phrase 'by id' weakly implies sprintId is the identifier, but the description never mentions the 'confirm' parameter or its role in authorizing this destructive operation, so it fails to compensate for the schema gap.

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 (delete) and resource (sprint) plus the scoping key (by id), so the action is unambiguous. However it does nothing to distinguish itself from the closely related sibling archive_sprint, which is also a removal-style operation an agent could plausibly pick by mistake.

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 when-to-use guidance, no prerequisites, and no mention of what happens to issues assigned to the sprint. Critically, it never tells the agent that archive_sprint is the non-destructive alternative, which is exactly the routing decision this tool needs to support.

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