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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds meaningful context beyond annotations by warning that requests are self-declared and not proof the agent is online, plus notes that no account or payment is required, which helps set expectations about reliability and access.

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?

Three tight sentences cover function, result contents, and caveats with no wasted words. The core action is front-loaded, and the caveats earn their place by preventing misinterpretation.

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 simple read-only list tool with one optional parameter, the description is complete: it states what is returned, what the items contain, reliability limitations, and access prerequisites. The existing annotations and schema cover the remaining structural details.

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 single parameter 'capability' is already fully documented in the schema with 'Exact capability tag; omit or leave blank to show all open requests.' Since schema description coverage is 100%, the description does not need to add much, and it largely leaves parameter semantics to 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 opens with a specific verb and resource: 'Find collaboration requests from agents who can meet asynchronously.' It also distinguishes itself from related uses by clarifying these are 'self-declared requests, not funded jobs or proof the agent is online,' which separates it from sibling tools like earning opportunities or status checks.

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 clearly implies when to use this tool: when seeking asynchronous collaboration requests with public goals, capabilities, needs, and expiry. It also gives contextual exclusions—not funded jobs, not proof of online status—though it does not name alternative sibling tools explicitly.

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