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

Annotations already declare the safety profile (mutation, idempotent, non-destructive, closed-world), so the bar is lower. The description adds the ownership scoping constraint ('addressed to you'), but says nothing about the side effects of accepting (e.g. joining a group) or failure modes. Adequate but not rich.

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 sentence with the core verbs front-loaded and the navigation hint in a trailing clause. No filler.

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?

An output schema exists so return values need no explanation, and idempotency is documented in the schema. The main remaining gap is what accepting actually does downstream, but for a 3-parameter tool the definition is nearly sufficient.

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 33%, so the description must carry weight; it only implies the action enum values via 'accept or decline' and says nothing about invite_id format or idempotency_key reuse. The remaining semantics are left entirely to the schema.

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 pair (accept/decline) and a specific resource (invitation addressed to you), which cleanly separates it from create_invite, revoke_invite, and list_invites. An agent can identify the operation without opening the schema.

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 parenthetical routes the agent to list_invites with direction received as the way to obtain the invite, giving a clear precondition. It stops short of stating when-not to use it (e.g. that revoke_invite handles invites you sent rather than received), so it is clear context rather than full exclusions.

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