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

Annotations provide a safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false). The description adds valuable beyond-annotation context: the $0.05/call cost, x402/USDC payment mechanism, and a clear independence disclaimer. This helps the agent anticipate cost and trust implications without contradicting 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?

The description is extremely concise: two sentences plus a payment clause. It is front-loaded with the action and resource, then provides essential cost and affiliation caveats. No wasted 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 description alone is brief, but the surrounding input schema is exceptionally detailed—covering all parameters, thresholds, cost caps, and output expectations in the schema's own description. The tool description adds the cost/payment and independence context that the schema lacks. With no output schema, the description still gives enough outcome context, and the schema's top-level description fills in the batch-size detail.

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% with rich per-parameter descriptions, so the baseline is 3. The description adds no extra parameter-level meaning beyond what the schema already provides.

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 uses a specific verb ('Convert') and identifies the exact resource ('official PPS contract aggregates') and the output ('buyer-agency demand priorities'). The title 'Korea G2B Contract Demand Radar' further distinguishes it from generic sibling tools like gov-tender-radar.

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?

There is no explicit when-to-use or exclusion guidance compared to alternatives. However, the Korea G2B domain is clearly implied by the title and description, giving some context for when this tool applies. No alternatives are named.

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