list-subscriptions

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

Describes pagination and sorting, and importantly discloses the Billforward limitation on period_start filters. No annotations, so description carries full burden; it could be more explicit about being read-only, but still strong.

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?

Two sentences plus a note, no waste. Purpose is front-loaded. Every sentence adds value.

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?

Covers purpose, usage context, and key behavioral nuance despite no output schema or annotations. Could hint at output structure, but adequate for a list tool with rich parameter docs.

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 covers all parameters with descriptions (100% coverage). Description adds extra semantic value by explaining the actual behavior of period_start filters, which is not clear from schema alone.

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?

Clearly states the verb (list), resource (subscriptions), and adds monitoring context for states and renewals, distinguishing it from siblings like get-subscription and cancel-subscription.

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?

Explicitly says when to use (monitor states/renewals) and provides a critical note about period_start filters being different from creation date filtering, but lacks explicit when-not-to-use or alternatives.

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