sonarr_get_config_indexer

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

Beyond the readOnlyHint: true annotation, the description adds no behavioral context. It does not mention any caveats, authentication requirements, or what the nested structure of 'indexer config' entails. The description relies entirely on the annotation for safety indication.

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 one concise phrase, 'List indexer config', with no wasted words. It is immediately understandable and appropriately sized for such a simple operation.

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 simple tool with no parameters, an output schema, and a read-only annotation, the description adequately identifies the operation. However, it lacks differentiation from the sonarr_get_config_indexer_by_id sibling, which could be important for selection, so it is not a perfect 5.

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, so the schema already fully covers parameter semantics. The baseline for 0 params is 4, and the description does not need to add parameter information. The description adds no redundant details.

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 'List indexer config' uses a specific verb ('list') and resource ('indexer config'), clearly indicating the operation. It distinguishes from the 'update' sibling and implies a collection operation, differentiating from the 'by_id' variant present in sibling tools.

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 like sonarr_get_config_indexer_by_id or sonarr_update_config_indexer. It does not state any context or exclusions, leaving the agent to infer usage solely from the name.

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