List subscription items

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only that results are paginated, a behavioral trait annotations do not express, but says nothing about default page size behavior, result ordering, or whether filters change the shape of the response.

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?

A single short sentence with the key fact (paginated list) front-loaded and zero filler. It is efficient, though its terseness borders on under-specification rather than ideal brevity.

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 six-parameter, all-optional read-only list endpoint with rich annotations and 83% schema coverage, no output schema is needed and the safety picture is complete. Still, the description omits the obvious filtering use case (subscription_id/price_id) and pagination defaults, leaving some practical gaps.

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 83%, so the schema itself explains account, include, per_page, price_id and subscription_id. The description contributes no additional parameter meaning, so the baseline of 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?

States a specific verb (list/return) and resource (subscription items) with a pagination qualifier, so the agent knows this is a collection-read endpoint. It does not differentiate itself from siblings such as list_subscriptions or get_subscription_item, which is the only missing element.

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?

No when-to-use guidance, no mention of when to prefer list_subscriptions versus this tool, and no note that the result can be narrowed by subscription_id or price_id even though the schema allows it. The agent gets no routing or filtering advice.

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