get_indexer_schema

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

With no annotations, the description carries the burden of conveying that this is a read-only schema-listing operation, and 'List' plus 'Use this as the template for create_indexer' makes that clear. It does not discuss edge cases or side effects, but none are likely for a schema retrieval tool, so the main behavior is transparent.

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?

Two tightly written sentences accomplish both the definition and the primary use case. There is no filler and the key behavior is front-loaded.

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 read-only schema tool with one optional parameter and no output schema, the description tells the agent what it returns and why to call it. Nothing needed for correct invocation is missing.

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 already documents the single optional implementation parameter with an example, so schema description coverage is 100%. The description adds context about listing every implementation, but it does not add parameter-level meaning beyond what the schema provides, matching the baseline for high coverage.

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 states a specific action ('List') and resource ('every indexer implementation Sonarr supports, with the fields each one takes'). It clearly distinguishes itself from siblings like get_indexer and create_indexer by identifying what it produces.

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?

It explicitly tells the agent to use this as the template for create_indexer, which is clear usage guidance. It does not name alternatives or exclusions, but the primary use case is obvious and still a strong signal.

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