sonarr_get_indexer

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

The readOnlyHint annotation already declares this as a read-only operation, and the description's 'Fetch' is consistent with that. The description adds the scoping constraint of 'single by id' but does not disclose other behavioral traits like error responses (e.g., 404 if not found). No contradiction exists, and the annotation lowers the bar, but little extra behavior is surfaced.

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 short, single sentence with no redundant fluff, which is appropriately concise. The grammar error 'indexers' (should be 'indexer') slightly detracts but does not affect comprehension. It earns its place by stating the core purpose efficiently.

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 getter with one parameter, the description is minimally viable: it states the action, resource, and key. The readOnlyHint and output schema cover safety and return types, but there is no mention of error behavior or how this tool fits with related list operations. Given the low complexity, this is adequate but not rich.

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 schema has one required integer parameter 'id' with no description, and the schema description coverage is 0%. The description only says 'by id', which essentially restates the parameter name without explaining what the id refers to, its domain, or any constraints. The description does not adequately compensate for the lack of schema documentation.

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" uses a specific verb (Fetch) and resource (indexer) and clearly indicates the granularity (single) and lookup key (by id). This distinguishes it from sibling tools like sonarr_list_indexer, which retrieves multiple indexers. Despite a minor grammar error, the purpose is 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 explicit guidance on when to use this tool versus alternatives such as sonarr_list_indexer or sonarr_get_indexerflag. It does not mention use cases, prerequisites, or exclusions. The only implied usage is that an id is required, but no context about when this is appropriate is given.

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