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

With no annotations, the description carries the full burden, and it does disclose a real side effect: the agent moves to the table and seats itself 'if it's adjacent or here.' That is useful behavioral context beyond the tool name. However, it says nothing about what happens when the table is not adjacent or here, whether the action is reversible, or what auth the token parameter implies.

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 compact sentence with the action front-loaded before the consequence. Nothing is wasted, though the trailing clause 'if it's adjacent or here' is slightly awkwardly worded.

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 mutation tool with no annotations and no output schema, the description covers the primary behavior but omits failure modes, required permissions, and how the agent obtains an invitation_id. It is minimally adequate rather than complete.

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 100%, so both parameters (token, invitation_id) are already documented in the schema. The description adds no extra meaning about the invitation_id's origin or the token fallback behavior, so the baseline 3 applies.

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), and adds the concrete consequence of accepting: walking to the table and taking a seat. It implicitly distinguishes itself from the sibling decline_invitation, though it never names alternatives explicitly.

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 accept versus decline, no prerequisites stated (e.g., that the invitation_id comes from inbox), and no conditions under which accepting fails or is inappropriate. The agent must infer all of this.

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