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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the exact cost ($0.002 USDC per successful call), the payment rail (x402 on Base, Solana or Arc), and that failed calls are not charged — precisely the billing behavior an agent needs before invoking. It also flags the coverage limitation of the returned data.

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?

Sources are front-loaded, coverage caveat and pricing follow in tight sentences; every clause carries information an agent would otherwise have to guess.

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, return-value explanation is unnecessary, and the description covers sources, recency windows, cost, and limitations. The one gap is the dangling reference to an optional buyer-country filter that is not in the input schema.

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% and the sole parameter (limit, 1–5, default 3) is fully documented in the schema, so the description need not repeat it. However, the description mentions 'buyer country optional' while the schema exposes no country parameter, which can mislead an agent about available filtering.

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 concrete verb+resource ('Latest public tender and contract items') and enumerates all three underlying sources (EU TED, UK Find a Tender, USAspending) with their time windows. This clearly separates it from single-source siblings like gov_ted_eu_procurement and gov_us_gov_contract_watch by positioning it as a consolidated feed.

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?

It states an explicit scope caveat ('Not a complete list of any one market'), which implies an agent should go to the single-source siblings for exhaustive coverage. It also gives the cost/charging condition up front. It stops short of naming the alternative tools or stating prerequisites, so it is strong but not complete routing guidance.

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