sonarr_delete_custom_format

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

The description states the action but offers no behavioral details. Since no annotations are provided, it should disclose that the deletion is permanent and irreversible, or any dependencies/restrictions, but it does not.

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, front-loaded sentence that states the action without any wasted words. It is appropriately concise for a simple deletion tool.

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?

The description is minimal but covers the basic operation. However, without annotations or output schema, it lacks any mention of irreversibility, error behavior, or side effects, leaving the description only partially complete.

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 already fully documents the single required parameter with a clear description. The tool description adds no additional parameter semantics beyond confirming the deletion is by ID.

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 uses the specific verb 'delete' with a clear resource ('custom format from Sonarr') and method ('by ID'). It clearly distinguishes from sibling CRUD tools like create/update/get custom formats.

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 usage guidance is provided. The description does not mention when to use this tool, prerequisites, or alternatives. It is only obvious from the name and description that it is for deletion.

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