list_recurring_plans

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

With no annotations provided, the description explicitly states 'Read-only,' which is an important behavioral trait for an agent to know. It also mentions optional filtering, but does not disclose limits, pagination, or error behavior. Still, the read-only declaration adds meaningful context beyond the bare listing.

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 single sentence with a parenthetical, no redundant content, and front-loads the core action. Every word earns its place.

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 simple list tool with one optional parameter and no output schema, the description covers the essential context: what it lists, the optional filter, and that it is read-only. It does not mention pagination or return format, but these are not critical for this simple use case.

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 schema covers 100% of parameters, with plan_id already described as optional and returning a single plan. The description repeats this via 'optionally filtered to a single plan.' Since the schema is fully documented, the description adds minimal extra parameter semantics but is not deficient.

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 uses a specific verb ('List') and resource ('recurring billing plans'), and clearly distinguishes from siblings like list_subscriptions or list_customer_vault by naming a unique resource type. The optional filter to a single plan is also stated.

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 implies when to use the tool (to list recurring billing plans) but does not compare it to alternatives such as list_subscriptions or get_subscription. No explicit exclusions or 'when not to use' guidance is provided.

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