entitlements_consume

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

Annotations already indicate a non-read-only, non-destructive, idempotent operation. The description adds context beyond annotations: the 'consumable SKU only' constraint and the effect on the purchase lifecycle. It does not detail error conditions, but this is adequate given the idempotentHint.

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 two short sections with bold headers, front-loading the purpose immediately. Every sentence adds value: purpose, constraint, effect, and return shape. No unnecessary verbiage.

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 two-parameter mutation tool, the description is complete: it states the purpose, the constraint, the return fields, and combined with the annotations covers safety and idempotency. The sibling list provides enough context for alternative operations.

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?

Both parameters have descriptions in the schema (coverage 100%), so the description does not need to add much. It does not enhance parameter semantics beyond what the schema provides, but remains at the baseline for full 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 clearly states the verb (mark as consumed), the resource (one-time entitlement), and the constraint (consumable SKU only). It explains the business effect (user's purchase recognized so they can buy again), which distinguishes it from sibling tools like entitlements_get or entitlements_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 provides a clear when-to-use context: for consumable SKUs when a one-time entitlement needs to be marked as consumed. It includes an explicit exclusion ('consumable SKU only'), though it does not name alternatives such as entitlements_get for checking status.

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