subscriptions__list_plans

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

With no annotations, the description carries the transparency burden. It discloses what the tool returns (prices, coverage, SHA, flags, notice) but does not mention read-only nature, auth requirements, rate limits, or pagination behavior.

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 that packs all relevant information. While dense, it is efficient and front-loaded with a context label. It could be slightly clearer with separation, but remains concise.

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?

Despite no output schema, the description enumerates key return fields (prices, coverage, SHA-256, readiness flags, notice), making it fairly complete for a list operation. It covers the essential aspects of the catalog.

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 tool has zero parameters (baseline 4). The description does not need to add parameter context, and it correctly omits any unnecessary parameter details.

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 clearly states the tool lists a versioned monthly-seat catalog with specific details (prices, coverage, SHA-256, readiness flags, confirmation notice). It uses a specific verb 'list' and resource 'catalog', distinguishing it from siblings like get_plan for single plans.

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 explicit when or when-not to use is provided. The description implies it is the comprehensive catalog listing, but does not guide the agent to prefer it over get_plan or other subscription tools for specific scenarios.

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