List plans

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes nothing beyond that: it does not mention the default limit of 10, the 100 max, cursor pagination semantics, or what the returned plan objects contain.

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 text is short and front-loaded, but the second sentence ("List your plans.") is a pure restatement of the first and earns no place. Brevity here reflects under-specification rather than disciplined editing.

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 list endpoint with four parameters including a nested date-range filter and cursor pagination, and with no output schema, the description should at least hint at return shape and pagination behavior. Neither is present, leaving the agent to infer everything from the schema alone.

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%, with the limit bounds, the created[gt/lt/gte/lte] filter example, and both cursor fields documented in the schema itself. The description adds no meaning on top of that, so the baseline 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?

"List plans. List your plans." restates the tool name and title without adding a specific scope, resource detail, or any differentiation from siblings such as get_plan or list_subscriptions. An agent learns only that it returns a collection of plan objects, which the name already conveyed.

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?

There is no guidance on when to use this versus get_plan (single plan retrieval) or list_subscriptions (plans are typically fetched to attach to a subscription). No prerequisites, no exclusions, no context about what a "plan" is in this API.

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