accept_invitation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Accepting an invitation' is a state-changing action, but the description doesn't disclose the Nth-value semantics beyond indexing (e.g., what happens if the user is already connected, whether the page must be open, what the response looks like). With zero annotations, this is a significant gap.

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, compact sentence that efficiently conveys the core operation. It's front-loaded and avoids wasted words. However, the 1-based indexing note could be better integrated or the description could add a bit more useful context without bloating.

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?

This is a state-changing action with no annotations, no output schema, and a single parameter that carries meaning beyond simply being a number. The description explains the indexing but omits behavioral details: whether the invitation manager page must be open, preconditions (being logged in, having pending invitations), error behavior for invalid nth values, and what the success/failure outcome looks like. For a mutating tool with zero annotations, this is under-specified.

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?

The description partially explains the single parameter 'nth' by clarifying it's 1-based. However, schema description coverage is 0%, meaning the schema itself provides no field descriptions. The description adds the 1-based indexing clarification but doesn't explain the maximum of 30, edge cases (e.g., nth beyond pending invitation count), or what happens with invalid values.

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 states a specific verb ('accept') on a specific resource ('pending invitation'), and clarifies 1-based indexing. However, it doesn't distinguish this from the sibling tool get_pending_invitations beyond the verb difference, and the resource is somewhat generic ('invitation manager page'). The purpose is clear but not fully differentiated.

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 implies this is for accepting pending invitations, which pairs with get_pending_invitations as a prerequisite (you'd need to see the list first). However, there's no explicit guidance on when to use this vs alternatives, no mention of checking the list first, no prerequisites stated, and no exclusion cases.

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