Quote a DIEM Agent Worker

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

With no annotations, the description carries the full disclosure burden. It adds useful traits ('free', 'exact-price') and implies a read-only quote operation, but it does not mention side effects, validity period, or error handling. The behavior is not fully transparent.

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?

The description is a single, front-loaded sentence with no filler. It efficiently conveys the core action, price characteristics, and target scope without unnecessary words.

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?

The tool is relatively simple (1 param, no output schema, no annotations). The description gives the essential purpose but does not describe the response format or any prerequisites. It is adequate for a basic quote tool but leaves gaps around return value structure and edge cases.

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 0%, so the description must compensate. However, it merely says 'for one worker', which adds little meaning beyond the schema's property name and enum. It does not explain what a 'worker' is or how to choose among the enum values, leaving the agent to infer from the parameter name.

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 tool's function: 'Return a free exact-price x402 USDC quote for one worker.' It uses a specific verb ('Return') and resource ('x402 USDC quote'), and distinguishes from siblings by focusing on quoting rather than listing or preparing calls.

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 makes the tool's purpose clear, implying it should be used when a worker quote is needed, but it does not explicitly mention when to use it over sibling tools like list_diem_workers or prepare_diem_worker_call. No explicit exclusions or alternatives are provided.

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