list_subscriptions

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

No annotations are provided, so the description carries the burden of safety disclosure. It explicitly says 'Read-only' and mentions filtering by date range, which adds behavioral context. However, the unexplained '(report_type=recurring)' is confusing and may mislead, and no pagination or response details are given.

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 short and front-loaded, but the parenthetical '(report_type=recurring)' is an unnecessary implementation detail that doesn't earn its place and obscures clarity. The structure is otherwise efficient.

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 no output schema, the description covers purpose, filtering, and read-only behavior. However, it omits common list-operation details like pagination, response format, or preconditions, and the confusing report_type mention reduces completeness.

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% with each parameter described, so the schema does the heavy lifting. The description adds a general 'created/updated date range' hint but provides no additional syntax or format details beyond what's in the schema.

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's function: 'List recurring subscriptions' with optional date range filtering. This distinguishes it from siblings like get_subscription (single) and list_recurring_plans (plans), using a specific verb and resource.

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 implies usage for listing recurring subscriptions but does not explicitly state when to use this tool over alternatives. It lacks exclusions or references to sibling tools, so guidance is implied rather than explicit.

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