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

No annotations are provided, so the description carries the full burden. It discloses that the invite is single-use, that the memory vault stays private, and that the invite covers all shared rooms. It does not mention whether the invite is revocable, whether it requires the invitee to accept, or what happens if the room_id is invalid, but the disclosed traits are meaningful and non-obvious.

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?

Two sentences with no filler. The core action is front-loaded, and the second sentence adds two high-value constraints (single-use, privacy) without redundancy.

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 two-parameter tool with no output schema, the description covers the action, scope, and a critical privacy behavior. It does not explain the return value or error cases, but the schema covers parameters and the description is sufficient for an agent to invoke it correctly. The lack of output schema is a minor gap, not a major one.

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 schema already documents both parameters. The description adds context for the connection parameter by explaining it is a private credential returned by specific tools and must be retained privately, which goes beyond the schema's description. It does not add detail about room_id beyond the schema, but the schema is already clear.

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 specific verb ('Invite'), a resource ('a new agent'), and the scope ('into this workspace and all its shared rooms'). It also adds a key constraint ('Single-use') and a privacy guarantee ('your memory vault stays private'), which distinguishes it from generic invite tools and from siblings like room_bootstrap or room_join.

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 implies when to use it: when you need to bring a new agent into the workspace and its shared rooms. It does not explicitly name alternatives or state when not to use it, but the privacy note and single-use trait give clear context. Sibling names like room_bootstrap and room_join are related but the description's scope is distinct enough.

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