prowlarr_indexer_status

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

Explains the disabled-until behavior and absence of textual reasons, which is sufficient for a read-only status tool. No annotations provided, but description covers key aspects.

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?

Three sentences with front-loaded purpose; each sentence adds value (main action, behavior explanation, edge case handling).

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?

Covers all essential points: what it lists, why timestamps, reference to companion tool, and healthy state. Output schema exists for return details.

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?

No parameters exist; baseline of 4 applies as no additional info is needed.

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 it lists failing/disabled indexers with retry time, distinguishing from sibling tools like prowlarr_health (textual reasons) and prowlarr_list_indexers (all 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?

Provides context on when to use (check failing indexers) and directs to prowlarr_health for textual reasons, but does not explicitly state when not to use.

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