prowlarr_grab

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

No annotations provided, so description carries the burden. It states the tool has an 'acquisition side effect' (mutation), explains category routing from Prowlarr UI, and details confirm behavior. This adds meaningful context beyond the schema, though it could mention rate limits or error cases.

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 three sentences, each serving a purpose: purpose, category routing detail, and parameter usage. It is front-loaded with the core action, no fluff or redundancy.

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 that an output schema exists (so return values are documented elsewhere), the description covers purpose, usage guidelines, and parameter semantics adequately. For a tool with 3 parameters and 0% schema coverage, this is 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?

Schema description coverage is 0%, so description must compensate. It explains guid and indexer_id come from prowlarr_search, and describes confirm's effect (dry-run vs actual grab). While it doesn't define the exact meaning of guid or indexer_id, it tells the agent where to obtain them, which is sufficient.

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 starts with a clear action: 'Send a release to Prowlarr's download client (acquisition side effect).' This specifies the verb (grab) and resource (release to download client), distinguishing it from siblings like prowlarr_search which searches for releases.

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 explicit guidance: 'Use the guid + indexerId shown by prowlarr_search.' It also clarifies the confirm parameter for dry-run vs actual grab. While it doesn't explicitly list when not to use, the context from siblings makes it clear this is for grabbing after searching.

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