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

The description adds behavior well beyond the annotations: it uses relevance ranking with price tie-breaks, returns a signed offer_token, attaches an approval card, gates apiosk_execute on user approval, and explicitly states it spends nothing. This is material operational context that readOnlyHint and idempotentHint do not convey.

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 compact sentences with no filler, and the core action is front-loaded. The first sentence is dense, but each clause contributes meaning, and the final 'Spends nothing.' is a short, high-value signal.

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 the output schema and safe annotations, the description covers the important interaction flow well: it explains the approval card, execution gating, and cost profile. It is not fully complete because it omits routing hints to sibling tools like apiosk_compare and apiosk_discover, but nothing essential about 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%, so the schema already fully documents quey, max_results, and max_price_usdc. The tool description mostly refers to output behavior and repeats 'plain-words job,' adding little parameter-level meaning beyond the schema.

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 action and resource: 'Return the single best runnable offer for a plain-words job,' and adds ranking and price tie-break criteria. It differentiates from apiosk_execute by noting approval must precede execution, but it does not explicitly differentiate from apiosk_compare or apiosk_discover.

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 gives clear operational context: this is the offer-selection step that produces an approval card and only apiosk_execute may follow approval. However, it never explicitly says when to choose this tool over apiosk_discover or apiosk_compare, so alternative usage has to be inferred from 'single best' and the title.

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