sonarr_list_indexer_schema

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

The description is consistent with the readOnlyHint annotation, but adds minimal behavioral context beyond stating it returns something. It mentions 'available fields/options' which gives a slight hint about output content, but does not describe format, pagination, or other behaviors. Given the annotation already marks it as safe, the description adds little extra transparency.

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, short sentence that directly states the purpose. Every word earns its place, and there is no redundant or filler content.

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 description is complete enough for a simple schema retrieval tool with no parameters and an output schema present. It correctly names the resource ('indexers') and conveys that it returns available fields/options. However, it does not explicitly connect this schema to indexer creation/updating workflows, which could add context.

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 description need not explain parameter semantics. The mention of 'available fields/options' is about output, not input. Under the baseline for 0 parameters, this is acceptable.

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 clearly states the tool's function: 'Return the indexers schema (available fields/options).' The verb 'Return' and resource 'indexers schema' are specific, and it distinguishes itself from sibling schema tools like sonarr_list_importlist_schema by explicitly naming 'indexers'.

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 implies usage (to retrieve the schema for indexers) but does not explicitly state when to use it versus alternatives. There is no mention of when-not-to-use or references to related tools like sonarr_list_indexer or sonarr_create_indexer.

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