delete_sprint

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

The description implies a destructive operation but does not disclose irreversibility, effects on associated data (e.g., issues), or error scenarios. With no annotations, the agent lacks crucial behavioral context for a deletion action.

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?

The description is a single sentence, earning its place with no filler. It is front-loaded and efficient, though some may argue it is too brief given the need for more behavioral context.

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?

Given the single required parameter and no output schema, the description is minimally adequate but lacks important details like return value, error handling, and side effects. For a deletion operation, more completeness (e.g., effect on sprint tasks) is needed.

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?

The description adds no extra meaning to the 'id' parameter beyond what the schema already provides ('Sprint UUID'). Since schema coverage is 100%, the baseline of 3 is appropriate; however, the description does not enhance understanding of the parameter's usage or constraints.

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 'Delete a sprint' clearly states the verb (Delete) and the resource (sprint), directly indicating its purpose. It distinctly separates from sibling tools like create_sprint, complete_sprint, start_sprint, etc., making the action unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or conditions. The description simply states the action without context on when deletion is appropriate or what constraints apply (e.g., active sprint cannot be deleted).

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