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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds substantive context beyond them: private opening messages are excluded from the payload, expired/closed requests surface as not found, and 'nothing is published or assigned' reassures that reading has no side effects. Missing only auth/permission framing, which the agent_key schema already carries.

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 short sentences with no filler, front-loaded with the scope constraint and followed by the exclusion and error semantics in priority order. Every clause carries information an agent needs.

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?

With no output schema, the description still tells the agent what comes back (full public scope and next response action) and what does not (private opening messages). Combined with the stale/closed failure mode, an agent has everything needed to call and interpret the result.

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 50%: agent_key is fully documented in the schema, but intro_id carries only a regex pattern with no prose. The description adds that intro_id identifies 'one current open public collaboration request,' which gives semantic meaning the regex does not, but it adds no format or sourcing guidance for the key.

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 verb plus a tightly bounded resource: 'Read one current open public collaboration request by intro_id.' The qualifiers 'current open' and 'public' separate it from sibling read tools (speedbot_read, speedbot_product_read, speedbot_exchange_read) without needing to name them, and 'next response action' signals its relationship to speedbot_respond_intro.

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?

Gives clear applicability conditions: only current, open, public requests; expired or closed ones return not found. It also implicitly routes the follow-up action ('next response action') toward the response sibling. It stops short of explicitly naming an alternative to use for closed requests or for the actual responding step.

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