sonarr_delete_metadata

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

The description's 'DESTRUCTIVE: this deletes data' merely repeats the annotation's destructiveHint=true and readOnlyHint=false. It adds no new context about side effects, dependencies, or reversibility, so it adds minimal value beyond structured data.

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 very short and front-loaded, but the DESTRUCTIVE warning is redundant with annotations, so not every word earns its place. Still, it is efficient and avoids fluff.

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 tool with one parameter and an output schema, the description is minimally adequate. However, it leaves the meaning of 'id' unspecified and does not mention any confirmation or side effects, which could be important for an agents' decision-making.

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% for the single 'id' parameter, and the description does not clarify what the id represents or how it should be used. The parameter name alone hints that it is the metadata provider ID, but the description fails to compensate for the missing schema documentation.

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 'Delete metadata providers,' which is a specific verb and resource. This distinguishes the tool from siblings like 'get_metadata' or 'update_metadata' in the CRUD family.

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 vs alternatives. The name implies deletion, but the description does not explain prerequisites, when deletion is appropriate, or what to consider (e.g., irreversibility).

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