accept_invite

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says the action is to accept an invite. It does not reveal potential side effects, whether the action is reversible, or that the confirm parameter must be true for the write to execute—info left entirely to the schema.

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 concise sentence with zero fluff. It is not front-loaded in a structured way, but it is appropriately short for a tool this straightforward, earning a strong score without reaching the higher bar of explicitly scoping or routing behavior.

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?

There are no annotations and no output schema, so the description must supply more context than just the action. It fails to mention the confirmation requirement, expected outcome, or relationship to list_invites/reject_invite, leaving an agent without enough behavioral context beyond the schema's parameter notes.

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 100%, so both parameters (inviteToken and confirm) already have meaningful descriptions, including that confirm must be true for the write operation. The tool description adds no additional parameter meaning, so the schema carries the full load and the baseline of 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?

The description uses a specific verb ('Accept') and a clear resource ('invitation token'), which states the core function in a complete sentence. It is not a tautology and is distinguishable from the sibling reject_invite by its opposite action, though it does not explicitly name that sibling.

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 offers no guidance on when to use this tool versus alternatives such as reject_invite or list_invites. It does not mention any prerequisites, such as needing to first obtain a token via list_invites, nor does it explain the confirm flag's role in executing the action.

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