get_list_subscription_plans

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

The description significantly expands on annotations by disclosing server-side auth injection, throttling and retry behavior, response shape, and error semantics for common HTTP statuses. It reinforces the read-only and non-destructive nature while adding operational detail that annotations alone do not provide.

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 well-structured with clear sections and front-loaded safety/read-only information. There is minor redundancy in saying 'Get a list' and then 'Returns a list of all subscription plans,' but every other sentence contributes useful operational context.

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 purpose, pagination, safety, authentication, rate limiting, and error handling. Nothing critical is missing for an agent to invoke and interpret the tool correctly.

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 coverage is 100%, and the description adds meaningful guidance on how to use the single parameter, 'page', by explaining pagination and the 50-item page limit. This goes slightly beyond the schema's basic parameter description.

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 gets a list of subscription plans, identifies the endpoint, and explains the sorting and pagination behavior. It also distinguishes the purpose from the related single-plan tool, get_subscription_plan, so the agent can select the right granularity.

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 explicitly says when to use the tool ('safe to call speculatively for lookups and reporting'), when not to use it ('Not for changing anything'), and points to the matching write tool. It mentions the related get_subscription_plan tool, though it does not fully specify the exact conditions for choosing one over the other.

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