List subscriptions

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: it does not mention the default limit of 10, the 100 max, pagination semantics, or what the response contains, leaving behavior undisclosed.

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?

"List subscriptions" appears twice verbatim, which is pure waste in a three-sentence description. The remaining sentence is short and front-loaded, but the duplication signals a copy/paste artifact rather than deliberate structure.

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?

With six parameters, a nested date-range filter, cursor pagination, and no output schema, the description should at minimum explain paging and the creation-time filter. It covers only two of six parameters and says nothing about return values or how to continue pagination.

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%, so all six parameters including the nested `created` filter and both cursors are already documented in the schema. The description's mention of `status` and `customer` only duplicates schema content, 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?

The description states a clear verb and resource ("List subscriptions"), but that is essentially a restatement of the tool name and title, and it makes no attempt to distinguish this list endpoint from siblings like get_subscription, create_subscription, or cancel_subscription. The only value-add is the mention of status/customer filtering.

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?

Filtering by `status` or `customer` hints at a retrieval use case, but there is no explicit guidance on when to call this versus get_subscription for a single record or versus other list tools. No preconditions, no mention of when a caller should page with cursors instead.

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