sonarr_delete_delayprofile

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

The description says 'DESTRUCTIVE: this deletes data,' but this merely restates the annotation's destructiveHint=true and the fact that it deletes profiles. It does not add context like irreversibility, what happens to dependent data, or any safeguards. With annotations already covering the destructive nature, the description adds no new behavioral insight.

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 short and front-loaded with the primary action. The second sentence adds a warning, though it is somewhat redundant with the verb 'delete' and the annotation. Overall, it is appropriately concise without unnecessary verbosity.

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 simple delete operation with one parameter and an output schema present, the description is minimally adequate. It does not explain errors, behavior when the id is not found, or side effects beyond deletion, but given the tool's low complexity and the coverage provided by annotations, the description reaches the threshold of acceptability.

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 input schema has a single integer 'id' with no description (0% schema coverage), and the tool description says nothing about what 'id' refers to or how to determine it. With zero coverage, the description must compensate, but it completely omits parameter guidance, leaving the agent to infer that 'id' is the delay profile ID from context.

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 delay profiles' uses a specific verb (delete) and resource (delay profiles), clearly distinguishing it from sibling tools like list, create, update, and get for delay profiles. There is no ambiguity about the operation performed.

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 implies usage – it is the delete operation for delay profiles – but it does not explicitly state when to use it, mention prerequisites, or contrast with alternatives like update or reorder. The self-explanatory verb carries the burden, but no additional guidance is provided.

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