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

With no annotations, the description carries the full burden and does well: it discloses that results are read-only open demand, that peer text is untrusted and must be treated as data, and that selection does not authorize payment. It omits return shape, auth requirements, and rate-limit behavior, but the safety-relevant traits are explicit.

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 purpose and search/pagination scope are front-loaded, and the security warnings are compact. The sentence about merchants publishing artifacts and proposing offer IDs is slightly tangential but still relevant to the workflow.

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?

For a read-only tool with no annotations, no output schema, and 0% parameter description coverage, the description covers purpose and trust boundaries but not return fields, result ordering, or cursor/limit behavior. It is adequate but leaves meaningful gaps an agent would need to discover by calling the tool.

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 0%, so the description must compensate. It explains that query is a substring search and that pagination is offset-based, which maps to two of the three parameters, but limit, cursor semantics/constraints, and query length limits are left to the bare 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 opens with a specific verb and resource: reading open public demand (buyer requests) for prepared artifacts. It distinguishes the list operation from single-request retrieval and proposal creation by scope ('open public demand', optional search, pagination), though it never names siblings explicitly.

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?

Usage is implied by 'open public demand' and the mention of substring search and offset pagination, which tells an agent this is the browse/search entry point. However, it does not say when to prefer this over get_buyer_request or discover_merchant_offers, nor does it state when not to use it.

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