radarr_get_indexer

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

The term 'Fetch' aligns with the readOnlyHint annotation, and no contradiction occurs. However, the description adds no additional behavioral context, such as error handling, response format, or side effects, beyond what the annotation and output schema already provide.

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 sentence, six words, and perfectly front-loaded with the action and resource. No wasted words or repetition, appropriately concise for a simple get-by-id 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 tool's simplicity (one parameter, readOnly annotation, output schema present), the description is sufficient for an agent to understand its purpose and usage. It lacks some nuance like returning 404 if not found, but the structured fields cover the essential safety and return expectations.

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?

With 0% schema description coverage, the description's 'by id' provides some semantic meaning for the single parameter, but it does not explain how to obtain the id, what type it should be (beyond schema's integer), or any special constraints. It adds minimal value over the schema.

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 indexers by id' clearly specifies a verb (fetch), resource (indexer), and scope (single by id). It distinguishes itself from sibling tools like radarr_list_indexer, which lists all indexers.

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 implies usage when a specific id is known ('by id'), but it does not provide explicit alternatives or exclusions. There is no guidance on when not to use this tool versus list_indexer or schema retrieval.

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