match_agents

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

Discloses important traits: results include unverified/low-trust agents, requires only one matching capability, and explains the ranking and payload_schema inclusion. No annotations to contradict.

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?

Well-structured with clear sections; every sentence adds value. While slightly longer, the information density justifies the length without redundancy.

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?

Covers all necessary aspects: purpose, parameters, return value (ranked list of trust objects with payload_schema), usage warning about schema mismatches, and prioritization of first result. No output schema needed.

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?

Despite 0% schema coverage, description explains 'capabilities' as a list of capability names with examples, and 'settlement_rail' as an optional filter with enumerated values, adding significant meaning 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?

Description starts with a specific verb 'Find agents that can handle the requested capabilities, ranked by a composite score', clearly distinguishing from sibling tools like 'verify_agent' and 'call_agent'.

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 states 'apply NO trust or verified gate' and 'ALWAYS call verify_agent on a result before transacting', providing clear when-to-use and alternative guidance.

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