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

No annotations are provided, so the description carries full burden. It discloses that the tool returns teasers (not full briefs), explains what teasers contain, and describes the paid unlock process. It also states that ranking already reads the full brief, so a teaser match is real. It does not mention any destructive actions, so it seems read-only.

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 long and information-dense, but could be more concise. It is front-loaded with the main purpose, but several sentences are detailed. Every sentence contributes, but overall it could be tightened.

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 complexity of the tool (matching buyers, teasers, paid tier), the description covers the main workflow well. No output schema exists, so the explanation of the return format (teaser fields, door_url, facets) is helpful. It does not mention any error conditions, which would be useful.

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?

The schema already describes both parameters with coverage 100%. The description adds meaning by explaining what to pass as query (e.g., 'raw selvedge denim') and that omitting query browses recent demand. This provides context beyond the 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 clearly states the tool discovers buyers actively looking for what you sell. It specifies the action 'discover' and the resource 'buyers with open briefs'. It distinguishes itself from siblings like find_seller and list_sellers by focusing on demand matching.

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?

The description explains when to use the tool (when you have something to sell, search by product) and when to omit query to browse. It provides context on how to use the teaser information and mentions the paid tier. However, it does not explicitly state when not to use or name direct alternatives.

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