sonarr_get_wanted_cutoff

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

Annotations already declare readOnlyHint=true, and the description simply says 'Fetch', which aligns with read-only behavior. No additional behavioral context (e.g., not-found errors, response details) is added beyond the annotation.

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, concise, front-loaded sentence with no filler. Every word contributes to understanding the tool's function.

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 get-by-id tool with one parameter, a readOnly annotation, and an output schema present, the description sufficiently communicates the core action. It does not explain domain-specific terms like 'cutoff', but given the sibling context, this is acceptable.

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 description coverage is 0% with one required integer parameter 'id'. The description's phrase 'by id' clarifies that the id parameter identifies which cutoff to fetch, adding meaning beyond the schema. However, it offers minimal additional detail.

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 'Fetch a single cutoff by id' uses a specific verb and resource, clearly distinguishing this get-by-id operation from sibling list operations like sonarr_list_wanted_cutoff. The addition of 'single' and 'by id' makes the intent unambiguous.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention that it is for fetching one specific record by ID, nor does it reference list_wanted_cutoff for retrieving all cutoffs.

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