list_subscription_offers

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only says 'List all offers' and does not mention permissions, pagination, read-only semantics, or the wildcard behavior of base_plan_id described in the schema. The read-only nature is implied by 'List' but not explicitly disclosed.

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 a single, front-loaded sentence with no filler or redundant information. Every word contributes to the purpose.

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 operation with a fully covered input schema and an output schema available, the description is essentially complete. It could be improved by mentioning the base_plan_id wildcard or alternative single-offer lookup tools, but it is sufficient for basic invocation.

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%, with package_name, product_id, and base_plan_id all documented in the input schema, including the '-' wildcard for base_plan_id. The tool description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

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 verb ('List'), the resource ('offers'), and the scope ('for a subscription base plan'). It distinguishes from singular/batch siblings like get_subscription_offer and batch_get_subscription_offers by emphasizing 'all offers'.

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 gives no explicit when-to-use guidance or alternatives. Sibling tools such as get_subscription_offer, create_subscription_offer, and batch_get_subscription_offers exist, but the description does not clarify when listing all offers is preferred over these alternatives.

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