radarr_get_config_indexer_by_id

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

ReadOnlyHint is already true, and the description's 'Fetch' is consistent with that. However, the description adds no behavioral context beyond the annotation—no details about 404 behavior, permissions, or how this differs from radarr_get_indexer. The tool is simple but the description contributes nothing extra.

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 sentence with no filler. However, the grammar error ('indexers' instead of 'indexer') slightly undermines clarity, and it's almost too terse to be informative.

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?

The tool is simple with one parameter, an output schema, and a read-only annotation. Given this, the description is minimally adequate but lacks explicit mention that this is a configuration indexer fetch and provides no usage context relative to similar tools. The output schema covers return values, reducing the completeness burden.

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 one integer `id` with no description (0% coverage). The description only says 'by id', implying the id parameter but not specifying what id refers to (indexer id vs config id) or any constraints. This is minimal compensation for the schema gap.

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 'Fetch' and identifies the resource 'single indexers by id', clearly indicating a retrieval operation. However, it doesn't explicitly distinguish this from sibling tools like radarr_get_config_indexer or radarr_get_indexer, so it's clear but not fully differentiating.

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 doesn't mention that this is for fetching a specific configuration indexer rather than listing all, nor does it reference any prerequisites or related tools.

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