offsets__buy_offset_budget

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

With no annotations, description carries full burden. It discloses never overspends, idempotent on purchase_id, dry_run preview without mutation, and ordering (cheapest-first). Does not cover failure modes or required permissions, but provides substantial behavioral insight.

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?

Efficient three-sentence description. First sentence gives core behavior, second gives use case context, third adds technical details (idempotency, dry_run). No wasted words, front-loaded with clearinghouse context.

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?

Covers core behavior and use case, but lacks details on error handling, return format (no output schema), and insufficient budget scenario. For a tool with 4 parameters and no output schema, the description is not fully complete.

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 has 0% description coverage. Description explains budget_minor (exact cost limit), purchase_id (idempotency), dry_run (preview), but buyer parameter is not elaborated. Provides meaning beyond schema types but not comprehensive for all 4 parameters.

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?

Describes a specific verb-resource (buy offset with budget constraint) and distinguishes from sibling tools like offsets__buy_offset by emphasizing money-denominated budget-based purchase. States it retires the maximum cheapest-first credits within budget_minor.

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?

Explicitly states it's for callers with a currency-based obligation (e.g., revenue share), and mentions idempotency and dry-run for preview. Does not directly name alternatives or state when not to use, but the context of budget vs non-budget is clear from sibling names.

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