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

Beyond the annotations, the description reveals important side effects: lazy creation of a per-App BotInstance user with isBot:true, live XMPP client spawning, and no required ai-service restart. This is exactly the kind of behavioral context an agent needs for a mutating, side-effectful operation.

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, front-loaded with the primary action, and every sentence earns its place by adding behavioral or usage detail. No filler or redundant restatement of the tool name.

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?

Together with the fully described schema and annotations, the description provides enough context for an agent to invoke the tool correctly: the action, the per-agent call pattern, the lazy creation side effect, and the operational consequence. The lack of an output schema does not hurt this side-effect-focused operation.

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 100%, so the parameter descriptions already carry the semantic weight. The tool description adds a useful 'once per agent' and 'per-App' framing, but it does not materially extend what the schema already states about parameters.

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 uses a specific verb ('Invite') and resource ('Agent into a chat room'), immediately clarifying what the tool does. It further distinguishes the operation from sibling agent-CRUD tools by describing an invitation/membership action with multi-agent behavior.

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 concrete usage context: call once per agent, multiple agents can coexist, and points to the quickstart prompt for the full multi-agent recipe. It does not explicitly name excluded alternatives, but the usage context is clear enough for an agent to decide when to invoke this tool.

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