prowlarr_indexer_proxies

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

With no annotations provided, the description carries the full burden. It discloses some behavioral traits: 'force_save bypasses validation', test operations run 'without saving', and actions can 'toggle status'. However, it omits side effects like whether delete is irreversible, any permission requirements, or rate limits, leaving partial 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 well-structured bullet list with each operation on its own line, making it easy to scan. It is longer than a single-sentence description, but the length is justified by the need to document nine distinct operations and their parameters. No superfluous words.

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 complexity (9 operations) and minimal input schema, the description does a solid job covering all operations, their parameters, and ordering hints like fetching schemas first. It does not provide example argument dictionaries, but the operation signatures are sufficient for a competent agent. The presence of an output schema reduces the need to describe return values.

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 input schema only defines 'operation' and a free-form 'arguments' object, so parameter semantics are entirely reliant on the description. The description provides detailed signatures for each operation, including required parameters (e.g., 'body is an IndexerProxyResource'), optional parameters (force_save=None), and cross-references to schema-fetching operations, adding meaningful guidance beyond the schema.

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 opens with 'prowlarr indexer proxies operations on Prowlarr' and then enumerates all supported operations with specific verbs (create, delete, get, list, test, update). This makes the tool's purpose clear and distinguishes it from sibling indexer tools, though the opening phrase is generic rather than a concise verb+resource statement.

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 clearly states this tool is for indexer proxy operations and even provides operational guidance, such as 'Read this before creating or updating a proxy' and noting that test operations do not save. It does not explicitly contrast with sibling tools, but the context is clear enough that an agent can infer when to use it.

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