firestarter_record_purchase

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

Annotations already indicate this is a non-readonly, non-idempotent write, and the description supplements that with useful behavior: the purchase history is consolidated so the item can be reordered later, and live keys are refused with TEST_MODE_ONLY. It doesn't cover duplicate handling or outputs, but adds meaningful context beyond the annotations.

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?

Three sentences, each earning its place: what the tool does, when to call it, and the environment limitation. The core purpose is front-loaded and no filler is present.

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 an 11-parameter write action with no output schema, the description gives enough guidance about invocation timing, accepted data breadth, and the test-mode restriction. It lacks explicit notes on response/error handling, but the schema and the 'whatever details' guidance mitigate that gap.

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 100%, so every parameter already has a description. The tool description adds some contextual guidance about 'whatever details are visible on the confirmation page' but doesn't explain individual parameters beyond what the schema provides. Baseline 3 is appropriate.

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 specific verb and resource: recording a purchase completed outside the network, with concrete examples (Lazada, Shopify) and the purpose of keeping unified purchase history and enabling reorders. It clearly distinguishes itself as the off-network recording tool from siblings that handle listings, imports, or delivery.

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?

It explicitly says when to call it — right after an off-network checkout succeeds — and gives context about using whatever confirmation-page details are available. It also states the live-key restriction, acting as a when-not-to-use condition. It doesn't name alternative sibling tools, but the guidance is clear enough for correct selection.

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