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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and 'Read-only' merely restates it. What the description does add is genuinely useful: the call returns a shareable invite link and a prefabricated message line, which tells the agent what it will receive and how to relay it, and the 'room you're in' phrasing implies a membership prerequisite. No output schema exists, so this return-value disclosure carries real weight.

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?

Three short sentences, front-loaded with the triggering use case, then the return value, then the safety profile. No filler and nothing out of order.

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 one-parameter read tool with full annotation coverage, the definition supplies everything an agent needs: when to invoke it, the membership precondition, and what comes back (link plus message line) despite there being no output schema.

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?

There is a single parameter with 100% schema description coverage, and that description already explains provenance ('Room id from list_rooms or check_in'). The tool description adds nothing about the parameter, so the baseline of 3 applies rather than a higher score.

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 first sentence names a concrete user goal (inviting a teammate and their AI into a room) and the second states the output precisely: the room's invite link plus a ready-to-pass line. The verb+resource is unambiguous, but no sibling tool is named, so the distinctness from neighbors like get_shared_context or check_in is only implicit.

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?

'Use when your user wants to bring a teammate (and their AI) into a room you're in' gives a clear triggering condition, including the membership premise. There are no stated exclusions or alternative tools for adjacent cases (e.g., when the user is not in the room or wants a different kind of sharing).

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