upservice_delete_sprint

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

Annotations already provide destructiveHint=true and readOnlyHint=false. The description adds the explicit statement of permanence ('Permanently delete') and confirms the return value as a JSON confirmation or error message, which supplements the annotations.

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 extremely concise: two lines of prose plus a structured args/returns section. Every sentence serves a purpose: stating the action, highlighting destructiveness, and specifying parameters and output format.

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 simplicity of the tool (single required parameter, no output schema needed beyond a string), the description covers the essential aspects: action, permanence, input, and return format. It could be slightly improved by noting that the sprint should not be active, but it is adequate.

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?

With 0% schema description coverage, the description only restates 'sprint_id (int)' without adding meaningful usage context or constraints beyond what the schema already provides (type and required status). The schema itself has a description for sprint_id, so the description adds minimal value.

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 'Permanently delete a sprint' with a specific verb and resource. The tool name and description effectively distinguish it from sibling delete tools (e.g., upservice_delete_project, upservice_delete_task) by focusing on the sprint resource.

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 explicit guidance on when to use or avoid this tool. No mention of prerequisites, alternatives, or situations where deletion might be inappropriate (e.g., active sprint). The description implies usage for deleting a sprint but lacks context.

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