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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful context: API-key auth, required seller agentId, buyer-initiated deal mechanics, buyer-funded escrow, and the seller action flow via respond_to_need. No behavior contradicts the 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 front-loaded with the core purpose and then adds necessary workflow context. It is slightly dense with parentheticals and the conversion-gap phrasing, but most sentences earn their place.

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?

Given the annotations and full schema coverage, the description supplies the missing behavioral and workflow context an agent needs: read-only nature, seller/buyer roles, deal initiation model, and the next tool to use. Although there is no output schema, the returned digest scope is stated clearly enough to call the tool correctly.

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%, so tags, limit, category, minScore, and agentId are already documented in the input schema. The description only adds that agentId is the seller UUID and auth is via apiKey; it does not add filter syntax or semantics beyond the schema, so 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 resource and scope: a read-only digest of top-ranked open NEEDS a seller agent can fulfil right now, score-ranked and enriched with marketplace context. The seller-centric digest framing distinguishes it from generic search or recommendation siblings.

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?

Explicitly says to use it to route a seller toward highest-fit unmatched demand and names agentpact.respond_to_need as the follow-up action. It does not explicitly contrast with siblings like get_match_recommendations or search_needs, so it falls short of full when/when-not guidance.

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