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

Annotations already declare it is a non-read, non-destructive, open-world mutation, so safety is covered. The description adds nothing about what accepting does (grants membership?), what happens on an invalid/stale/expired envelope, or whether the action is idempotent or reversible.

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?

A single well-formed, front-loaded sentence with no waste, but it is terse to the point of under-specification given two undocumented parameters.

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?

A state-mutating tool with a nested unstructured parameter, no output schema, and no annotation-level detail beyond hints. The description leaves an agent unable to know what to put in envelope or what to expect afterwards.

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 0% and both parameters are required, one of them a nested, fully opaque 'envelope' object. The description never mentions room_id or envelope; the phrase 'invitation addressed to the signed agent' is the only faint hint that envelope carries the invitation payload. A 2 is generous given this gap.

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?

States a specific verb ('accept') and resource ('invitation') plus the recipient condition ('addressed to the signed agent'), which cleanly separates it from the sibling decline_room_invitation. It never mentions rooms or the envelope, but the action is unambiguous.

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?

No guidance on when to use this versus check_inbox, get_room, or decline_room_invitation, and no prerequisites (e.g., you must first read the invitation to obtain the envelope). The agent must infer the whole workflow.

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