Create Subscription Offer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the tool is 'Disabled in read-only mode,' indicating a mutating operation, but it does not mention side effects, prerequisites, idempotency, whether creating with an existing offer_id fails or replaces, or any other behavioral traits.

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 brief and front-loaded with the core action. The second sentence about read-only mode earns its place as an important operational constraint. Slight redundancy exists between the title and the first sentence, but overall it is efficient.

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?

The tool has six parameters, a nested 'offer' object, and many closely related siblings, yet the description provides only the basic create action and the read-only note. It does not explain the relationship to the parent plan/product, what the offer resource should contain, or when creating is appropriate. The output schema reduces the need to describe return values, but the operational and domain context is still thin.

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%, so the schema already documents all six parameters. The description adds no parameter-level meaning beyond the schema, which matches the baseline of 3 for full schema coverage.

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 states a clear verb and resource: 'Create a new subscription offer.' This is unambiguous and distinct from sibling tools like get_subscription_offer, patch_subscription_offer, or delete_subscription_offer, though it does not explicitly name those alternatives.

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 guidance is provided about when to use this tool versus alternatives such as patch_subscription_offer for modifying an existing offer. The only usage-related context is 'Disabled in read-only mode,' which is a constraint, not a usage guideline. There are no when-to-use or when-not-to-use instructions.

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