sonarr_create_customformat

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

The description says 'WRITE: this modifies your Sonarr instance,' which merely restates the annotation readOnlyHint=false. It adds no additional behavioral details such as what specifically gets modified, authentication needs, rate limits, or side effects. No contradiction with 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 two short sentences. The first clearly states the action, the second warns about side effects. Both sentences are informative and front-loaded with no filler.

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 create operation with an opaque body, the description is severely underspecified. It lacks any information about the structure of a custom format, required fields, or typical usage. While an output schema exists, the description still fails to provide enough to invoke the tool correctly.

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 'body' parameter with additionalProperties:true and no description. The description does not explain what fields the body should contain for a custom format, no examples, and no reference to a schema. With 0% schema description coverage, the description fails to compensate.

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 states 'Create custom formats' with a specific verb and resource. The verb 'create' clearly distinguishes it from sibling tools like sonarr_update_customformat, sonarr_list_customformat, and sonarr_delete_customformat.

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 versus alternatives. It does not mention prerequisites, exclusions, or related tools. The 'WRITE' label only warns about mutation, not about usage scenarios.

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