sonarr_create_custom_format

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

No annotations are provided, so the description carries the full burden. It states that it creates a new format, which implies a write operation, but it does not disclose potential side effects such as duplicate name errors, whether it overwrites existing formats, or what the response contains. This is insufficient for a mutation tool.

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 two short sentences with no fluff. It front-loads the primary action and then adds the key requirement. Every word earns its place, and it is appropriately brief for a simple create 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?

Given the moderate complexity (nested objects, no output schema), the description is too thin. It does not explain expected return values, error conditions, or idempotency. The 'full specifications array' hint is useful but not sufficient to fully guide an agent invoking this tool.

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 100%, so the baseline is 3. The description adds a mild hint that the specifications array must be 'full', emphasizing completeness, but does not significantly enhance understanding beyond the schema. No additional parameter details are provided for includeWhenRenaming.

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 the action 'Create' and the resource 'custom format in Sonarr', distinguishing it from sibling tools like update, list, get, and delete. It also adds the scope of defining matching rules via a specifications array.

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 usage is implied by the verb 'Create' but there is no explicit guidance on when to use this versus update, or any prerequisites like listing existing formats first. It does not mention alternatives or exclusions, so it relies on the user to infer intent.

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