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

Beyond the annotations, the description discloses authentication needs, a required capability, the concrete side effect of building a three-person group and sending an opener, cloud-user restrictions, a daily cross-organization limit, and a previewHash-based reconfirmation rule. These are exactly the behavioral traits an agent needs for safe invocation.

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?

The description is compact and front-loads login and capability requirements before moving to limits and the preview workflow. The dense bracketed structure is efficient, though slightly harder to scan than plain prose.

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 non-read-only introduction tool with no output schema, the description covers prerequisites, capability limits, daily quota, side effects, preview workflow, and reconfirmation conditions. An agent has enough context to call it correctly.

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 80%, so the baseline is 3. The description adds execution semantics by explaining that preview verifies names and the full message, and that execution requires the same parameters plus previewHash with preview=false, and that any content or roster change forces reconfirmation.

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 states a concrete effect: creating a three-person group and sending an opener for an organization match pair. It is clear what the tool does, though it does not explicitly differentiate this introduce action from sibling tools such as introduce_broker_match or introduce_organization_proposal.

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?

It gives clear prerequisites (login required, group-creation ability needed), exclusions (cloud users cannot create groups), a rate limit (10 cross-organization introductions per day), and an explicit preview-confirm-execute workflow. It lacks routing guidance to sibling alternatives, but the usage context is strong.

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