subscription_offers_list

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

With no annotations, the description should carry full behavioral transparency. It adds value by disclosing the wildcard behavior for basePlanId, but it omits details about read-only nature, pagination handling, authentication needs, or response format.

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 extremely concise with two sentences. It is front-loaded with the core purpose, and every word adds value with no unnecessary fluff.

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?

Given the tool has 5 parameters, no annotations, and no output schema, the description is moderately complete. It covers the basic purpose and a key parameter nuance but lacks detail on pagination, return values, or any constraints beyond the wildcard.

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 low (40%). The description adds useful context for the basePlanId parameter (wildcard support), compensating somewhat. However, it does not explain the other two undocumented parameters (pageSize, pageToken) beyond what the schema provides.

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' and the resource 'offers for a base plan'. The mention of the '-' wildcard for basePlanId distinguishes this tool from sibling list tools by highlighting a unique feature.

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 clear context: use this tool to list offers under a specific base plan, and the wildcard ability to list across all base plans. However, it does not explicitly mention when not to use it or suggest alternatives like subscription_offers_get for single offers.

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