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

Annotations already declare readOnlyHint and idempotentHint, and the description adds meaningful behavioral context beyond them: it 'Spends nothing', returns a signed offer_token, and requires explicit user approval before any execution. This gives the agent a clear side-effect and workflow picture.

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?

One dense, front-loaded sentence conveys purpose, return contents, and workflow, followed by a compact safety note. No filler or repetition of the schema; every clause adds value.

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?

With an output schema present and annotations already covering read-only/idempotent behavior, the description supplies the remaining context: approval flow, no cost, and the handoff to apiosk_execute. Nothing essential for selecting and invoking the tool is missing.

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 description coverage is 100%: query, max_results, and max_price_usdc are already fully documented in the schema. The description reinforces the concept of price but does not add parameter semantics beyond what the schema provides, so the baseline of 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?

States a specific verb ('Return'), a precise resource ('single best runnable offer'), and the selection mechanism (relevance ranking and price tie-breaks). Also lists the concrete return fields, making it distinct from broader discovery/compare siblings. The mention of apiosk_execute as the follow-up clarifies its role in the workflow.

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?

Gives clear context: use for a plain-words job where a single best offer is wanted, and indicates that approval is required before moving to apiosk_execute. It does not explicitly rule out sibling tools like apiosk_compare or apiosk_discover, so it stops short of the strongest when-not guidance.

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