get_subscription_invoices

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

The description discloses pagination and the include parameter for detail/transactions, which is useful. But with no annotations, it should also mention auth requirements, error handling, or response format. The information is basic but not comprehensive.

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?

Three concise sentences: purpose, endpoint, usage hint. No redundant information, each sentence adds value. Well front-loaded with the verb and resource.

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?

No output schema; description only says 'Returns paginated invoices.' Missing details on pagination metadata structure, invoice fields, and error states. Given 4 parameters and no output schema, the description is insufficient for an agent to fully understand return values.

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 input schema has 100% coverage with descriptions, so baseline is 3. The description adds a clear usage example for the include parameter ('e.g. include=detail,transactions'), which enhances understanding beyond the schema's comma-separated list.

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 action (list) and resource (invoices for a subscription) with a specific endpoint. However, it does not explicitly differentiate from siblings like get_customer_invoices or list_invoices, which also return invoices.

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 provides context for usage (listing invoices for a subscription) but offers no guidance on when to use this tool versus alternatives like get_customer_invoices or list_invoices. No exclusions or prerequisites are mentioned.

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