update_subscription_offer

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose meaningful semantics — that this is a partial, mask-driven replace rather than a full overwrite, and that only the listed fields are replaced while others are preserved. It says nothing about required permissions, edit-lifecycle prerequisites, reversibility, or propagation effects (the latencyTolerance param hints at async propagation that is never explained).

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?

Two tight sentences with the action front-loaded and the two most confusing parameters explained immediately after. Nothing is padded, though it is so terse that it omits context that would have earned its place.

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?

This is an 8-parameter mutation with a nested object, no annotations, and no output schema, so the description must do more than explain two fields. It covers the mask/body mechanics adequately but leaves the edit-transaction model, permission requirements, and the interaction between required identifiers and the mask unexplained.

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 coverage is 63%, so the schema documents roughly half the inputs and the description must fill gaps. It does add the most valuable missing meaning: updateMask is a comma-style field list with concrete examples ('phases', 'regionalConfigs', 'offerTags') and offer carries the replacement values, neither of which the schema describes. However, offerId and basePlanId remain undocumented in both places, and nothing explains how regionsVersion or latencyTolerance interact with the patch.

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 opens with a specific verb+resource pair ('Patch a subscription offer'), which is clearly distinguishable from the create/activate/deactivate/delete siblings in the same family. It stops short of naming any sibling or stating the differentiating condition, so it does not reach a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of preconditions such as working inside an edit transaction (the presence of commit_edit/delete_edit siblings suggests edits are a real lifecycle concern the agent must know about). Usage is only inferable from the word 'Patch'.

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