list_r2_pipelines

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses nothing about pagination, result limits, ordering, or whether summary or full pipeline details are returned. 'List' implies a non-destructive read, but that is inferred from the verb rather than stated.

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?

A single sentence that front-loads the verb and resource, with zero waste. Every word serves a purpose: 'List' (operation), 'R2 pipelines' (resource), 'for an account' (scope). Appropriate size for a one-parameter list tool.

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?

The tool is simple (one required param, no nested objects), and the description covers what it does and the scope. However, there is no output schema and the description does not hint at the return shape, pagination behavior, or whether the response is a plain array or a wrapped object, leaving a meaningful gap for an agent.

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 100% — the account_id parameter is already documented as 'The account ID.' The phrase 'for an account' mildly reinforces the parameter's meaning but adds nothing beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb ('List'), a specific resource ('R2 pipelines'), and a specific scope ('for an account'). An agent can unambiguously distinguish this from the sibling get_r2_pipeline (singular retrieval vs plural listing) and list_r2_buckets (different R2 resource) without opening either schema.

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?

No guidance is provided on when to use this tool vs alternatives. There is no mention of get_r2_pipeline for single-pipeline lookup, no exclusions, and no context about scenarios where listing all pipelines is appropriate. The only hint is 'for an account,' which ties to the required parameter but does not help an agent choose between siblings.

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