sonarr_list_indexer

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

The annotation readOnlyHint=true already communicates that this is a safe read operation. The description adds no additional behavioral context, such as pagination, return format, or access requirements. It is consistent with the annotation, so no contradiction, but contributes minimal value beyond the structured data.

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 unnecessary words. It is front-loaded and to the point, making it highly efficient for an agent to parse.

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, output schema present, and read-only annotation), the description is sufficient for an agent to understand the operation. It could potentially mention that it returns all configured indexers, but the output schema likely provides that detail, making the description adequate.

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 is fully covered (empty properties). According to the rubric, a baseline of 4 is appropriate when no parameters exist, and the description does not need to explain parameter semantics.

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 indexers.' uses a specific verb and resource, clearly indicating the tool lists indexers. However, it lacks explicit scope (e.g., 'all') and does not differentiate from the sibling tool sonarr_list_indexer_schema, though the resource names differ.

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, such as sonarr_get_indexer for a specific indexer or sonarr_list_indexer_schema for schemas. The description is purely functional with no contextual usage information.

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