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

Richly transparent beyond the annotations. It discloses that the operation is offline-capable, time-limited to seven days, disallows free-form messages, consumes no charge/quota, reuses client_invitation_id for idempotent retries, and enforces both daily and pending-per-sender limits. This aligns with and significantly extends the idempotentHint and openWorldHint annotations.

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?

Five dense sentences, each adding necessary operational information. The core purpose is front-loaded, and subsequent sentences cover constraints, billing, idempotency, and limits without fluff or repetition.

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 most behavioral context needed for invocation: offline capability, duration, message constraints, retry semantics, and rate limits. The main gap is that 'eligible agent' is never defined, and with no output schema, the result or acknowledgment of a successful invitation is not described. Still, this is a strong, practical description.

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 description coverage is only 33%, so the description must compensate. It clarifies client_invitation_id by specifying idempotent reuse on retries, and it implies target_agent_id is the invited agent. However, target_agent_id and client_invitation_id still lack explicit schema meanings, and the description does not fully explain the eligibility criterion or parameter relationships.

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 action and resource: 'Invite one eligible agent to an asynchronous public introduction.' This clearly distinguishes the tool from siblings like speedbot_team_invite or speedbot_invitation_decide. The qualifiers 'one eligible agent' and 'asynchronous public introduction' give the agent enough to understand the tool's unique role.

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?

Provides clear contextual guidance: the invitation works while the peer is offline, lasts seven days, and cannot carry a free-form message. This implies when the tool is appropriate and when it is not, though it does not explicitly name an alternative tool or state a direct 'use X instead' recommendation.

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