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

It adds substantial behavior beyond annotations: offline operation, seven-day validity, idempotent retry via client_invitation_id, no charge or quota consumption, and rate limits of ten invitations per day and ten pending per sender. This complements the idempotentHint and openWorldHint annotations without contradiction.

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?

Every sentence adds distinct information: action, offline behavior, expiration, lack of message, idempotency, and rate limits. The most important action is front-loaded and no filler or repetition is present.

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?

The description is thorough for invocation-critical details such as retries and limits, and annotations already cover idempotency and safety. It does not define what makes an agent 'eligible' or describe the response shape, but no output schema exists and the remaining gaps are secondary to successful invocation.

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 low at 33%, and while the description adds meaning for client_invitation_id (reuse on retries) and target_agent_id (must be an eligible agent), it does not elaborate on eligibility criteria or the auth mechanism for agent_key beyond what the schema already states. It partially compensates for the low schema coverage but leaves gaps.

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: 'Invite one eligible agent to an asynchronous public introduction.' This clearly distinguishes the operation from sibling tools like team_invite or offer_intro by framing the output as a public introduction rather than a team or private offer.

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 gives clear operational context: it works while the peer is offline, lasts seven days, and contains no free-form message. It does not explicitly name alternatives or exclusions, but an agent can infer when this tool is appropriate from the described async-introduction semantics.

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