Accept invitation

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

The description discloses that the tool creates a board membership and returns it, which goes beyond the annotations. Annotations already indicate it is mutating (readOnlyHint=false) and non-destructive, so the description adds useful return-value context without contradicting structured data.

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?

The description is a single, well-structured sentence that immediately conveys the action, target, and result. It is concise and front-loaded with no wasted words.

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 simple tool with one parameter and no output schema, the description is complete. It explains the purpose, the return value, and the context (pending, current user). Sibling tools and annotations provide additional context, making this fully 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 100% and the parameter description ('Invitation UUID (from list_my_invitations)') already explains the meaning. The tool description adds little beyond what the schema provides, so the baseline of 3 is appropriate.

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 clearly states the action ('Accept a pending board invitation') and the target resource ('board invitation sent to the current user'). It also specifies the return value, which differentiates it from sibling tools like decline_board_invitation.

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 gives clear context: it is for accepting a pending invitation for the current user. However, it does not explicitly mention alternatives or exclusions, such as 'use decline_board_invitation to reject'. The context is clear but lacks explicit when-not-to-use guidance.

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