subscription_offers_create

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

With no annotations provided, the description must disclose behavioral traits, but it only states the creation action. It does not mention side effects, prerequisites, permissions, error states, or what happens if the offer already exists, leaving significant gaps.

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 11 words, containing no extraneous information. Every word is purposeful, making it highly concise and easy to parse.

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's complexity (6 parameters, nested objects, 5 required, no output schema), the description is far too minimal. It fails to explain the offer structure, regionsVersion, or preconditions, leaving the agent underinformed for proper 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 low (33%), and the description adds no parameter-level information. It only references 'base plan' but fails to explain the offer object structure, required fields, or the regionsVersion parameter, which is critical for usage.

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 creates an offer on a base plan, with explicit examples like free trial and intro pricing. It provides a specific verb and resource, distinguishing it from sibling tools like subscription_offers_get or subscription_offers_list.

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 creating new offers on base plans, but lacks explicit guidance on when to use this tool versus alternatives (e.g., subscription_offers_activate for activating existing offers). No when-not or alternative conditions are provided.

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