List subscriptions

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

With no annotations provided, the description carries the full disclosure burden. It clearly states 'Read-only' and adds the behavioral detail 'Reads every page,' which is genuinely useful for an AI agent. It does not cover error behavior or response shape, but for a simple read tool this is solid.

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 short sentences with no fluff. The core action and scope are front-loaded, read-only safety is stated immediately, and every sentence adds information.

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?

For a one-optional-parameter, read-only listing tool, this is nearly complete: it names the resource, the filter, the content of results, and pagination behavior. The lack of an output schema means the exact return shape isn't described, but the stated 'state and Features' gives an agent enough to judge suitability.

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 only parameter, customer_ref, is already documented in the schema. The description restates that the parameter optionally restricts to one customer, adding little beyond the structured definition. Baseline 3 is appropriate.

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 names a specific resource ('ProAbono subscriptions') and a precise action ('Lists'), with scope qualifiers ('optionally those of one customer'). It also clarifies what data is included ('state and the Features they carry'), which distinguishes it from siblings like list_offers and list_features.

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?

It gives explicit use cases: 'see what a customer is actually subscribed to' and 'explain why a customer has no rights.' It stops short of naming alternatives or saying when not to use this tool, but the intended context is clear.

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