radarr_list_customformat

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

Annotations declare readOnlyHint=true, and the description ('List') is consistent with that. However, the description adds no behavioral details beyond the annotation, such as pagination, response format, or that it returns all custom formats. With annotations already covering safety, a neutral score is appropriate.

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, well-structured sentence using only three words. It is front-loaded and every word contributes to the meaning. No unnecessary detail is present, making it highly concise.

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 tool's simplicity (no parameters, read-only, output schema present), the description is complete enough. The agent can infer the return value from the output schema, and the purpose is unambiguous. There are no hidden prerequisites or complex behaviors requiring additional explanation.

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 tool has zero parameters, and the schema covers 100% (vacuously). Per the rubric, 0 parameters gives a baseline of 4, and the description does not need to add parameter details. No additional explanation is required.

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 a specific verb ('List') and resource ('custom formats'), clearly distinguishing it from siblings like radarr_get_customformat (singular retrieval) and radarr_list_customfilter (different resource type). The purpose is immediately clear.

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. There is no mention of the sibling radarr_get_customformat for individual retrieval, nor any context about typical use cases. The description simply states what it does, leaving usage entirely implied.

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