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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds meaningful context beyond them: data freshness (updated every 3 hours), source provenance (National Treasury eTenders portal), and a paid access requirement ($0.005 USDC per call via x402 on Base mainnet). The payment detail is important operational context an agent would otherwise miss. It stops short of describing pagination limits or failure modes, so not a 5.

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?

Front-loaded with the resource and scope, followed by filters, return fields, freshness, and cost — a logical order with no filler. Slightly dense as a single run-on sentence, but every clause carries information.

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 no output schema, the description compensates by enumerating the returned fields (tender number, description, buyer, procurement method, dates, document links). Combined with the freshness and pricing notes, an agent has enough to decide and invoke correctly; only pagination/result-volume behavior is unaddressed.

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 explains every parameter including defaults and ranges. The description only summarizes the filter dimensions (keyword, closing date, category, buyer) without adding syntax or format detail beyond the schema. Baseline 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 and resource — searching open South African government tenders and RFQs from the National Treasury eTenders portal — and names the exact coverage (national/provincial departments, municipalities, SOEs). No sibling tool in the list does anything similar, so an agent can route to it unambiguously.

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 for when the tool applies (open tenders/RFQs from SA public bodies) and lists the filtering levers an agent would use. It does not state exclusions or point to an alternative, but no sibling overlaps, so the practical guidance is sufficient.

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