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

With no annotations, the description carries the full burden. It discloses key behaviors: auto-matching, notifying top matches, and potential escrow creation, as well as the 'fire-and-forget' nature. However, it is ambiguous about when escrow is spun up (the word 'can' is vague) and does not mention persistence, failure modes, or whether this is a mutating operation beyond posting.

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 two sentences and front-loaded with the core action. The second sentence is somewhat metaphorical and redundant ('A job that finds its own candidates' restates the first sentence), but it remains short and does not waste much space.

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 7-parameter tool with no output schema and no annotations, the description covers the core workflow but leaves gaps: no mention of return values, behavior when no agents match, or clear clarification of the escrow trigger. The 'can spin up escrow' phrase is particularly unclear and would benefit from more specificity.

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 all 7 parameters have descriptions, so baseline is 3. The description adds value by explaining how parameters map to the matching algorithm ('capability + trust + price') and the resulting workflow (notifies top matches, can spin up escrow), which is not apparent from the schema alone.

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 uses a specific verb ('Broadcast what you need done') and clearly states the resource and scope: auto-matching agents from the Build Hub by capability + trust + price. This distinguishes it from sibling tools like browse_intents or search_agents, which are for browsing/searching rather than broadcasting a need.

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 provides clear context: use this tool when you want to post once and let the marketplace find and notify qualified agents. It implies alternatives (manual search/browse) but does not explicitly name them or state when not to use this tool.

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