purchase-domain

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

Annotations already indicate destructive and non-read-only. Description adds critical details: irreversible, charges card, user confirmation needed, returns a purchase_id for polling. No contradictions.

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 packed with essential info: action, warning, prerequisite, side effect, next step. No filler.

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?

Given one parameter, no output schema, and high annotations, the description covers all needed context: input origin, irreversible effect, billing action, confirmation requirement, and follow-up polling URL.

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% coverage, so description must compensate. It describes the purchase-token parameter's origin, purpose, and validation (expired tokens rejected). Exact schema details like property names are missing, but the key semantic is clear.

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 action ('Execute a domain purchase'), the required input ('purchase-token obtained from quote-domain-purchase'), and the irreversible nature. It distinguishes itself from sibling tools like quote-domain-purchase and get-domain-purchase-status.

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 says when to use ('after obtaining purchase-token'), prerequisites ('explicit user confirmation of quoted amount'), and alternatives (poll with get-domain-purchase-status). No ambiguity.

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