radarr_get_indexerflag

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

The annotation readOnlyHint=true already indicates a safe read operation. The description's verb 'List' is consistent with this, but it adds no extra behavioral context such as what data is returned or any limitations. With the annotation covering the safety profile, a neutral score is appropriate.

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 sentence, 'List indexer flags.', which is precisely the essential information. It is front-loaded and contains no filler or redundant phrasing.

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, readOnlyHint annotation, and an output schema — the description is minimally sufficient. It doesn't explain what 'indexer flags' are, but the output schema likely provides that detail. For a straightforward list operation, this is adequately complete.

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 cannot add parameter meaning. The schema already documents this fully (100% coverage). Baseline of 4 is warranted due to the absence of parameters.

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 indexer flags.' clearly states the verb 'List' and resource 'indexer flags', which is specific and unambiguous. It does not explicitly distinguish from sibling tools, but the resource name is unique enough to avoid confusion.

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?

There is no guidance on when to use this tool versus alternatives. The description is purely a statement of function without any context, exclusions, or references to related tools like radarr_list_indexer for general indexer operations.

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