sonarr_get_indexerflag

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

The description simply restates what the name implies and adds no behavioral context beyond the readOnlyHint annotation. It does not disclose return format, pagination, or any other operational details.

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, clear sentence with no wasted words. It is front-loaded and immediately conveys the tool's purpose.

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 zero-parameter, read-only list tool, the description is adequate. It clearly states the action and resource, and the presence of an output schema compensates for the lack of return-value explanation. A slight caveat is that 'indexer flags' could use a brief clarification, but overall it is complete enough for a simple operation.

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?

With zero parameters and no schema properties, there is nothing to explain. The baseline for zero-parameter tools is 4, and the description correctly omits any parameter information.

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 uses a specific verb ('list') and a distinct resource ('indexer flags'), clearly distinguishing it from sibling tools that manage indexers (e.g., sonarr_list_indexer, sonarr_get_config_indexer). The name itself reinforces the resource.

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 the many other listing tools in the sibling set. It lacks any mention of alternatives, prerequisites, or exclusions.

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