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

Annotations declare destructive/openWorld but not the specifics; the description adds real value by naming the side effects: switching the active connection to that company and best-effort emailing other members. It falls short of 5 because the canonicality/idempotency/prerequisite lines are generic boilerplate rather than tool-specific facts.

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 core sentence is front-loaded and useful, but the back half is templated filler ('Canonicality...', 'Idempotency: obey the tool-specific retry key or guarantee...', 'Confirmation boundary...') that repeats generic policy rather than conveying redeem_invite-specific information.

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 destructive, non-read-only mutation with no output schema, the description covers confirmation, prerequisites, and concrete side effects, which is enough to invoke it safely. Return-shape guidance is absent but the description does point the agent at the returned actual_tool_output.

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 0% for two parameters. The description only implies joinCode is an invite code; the _corply_context object (id/receipt) is never explained in either the schema or the description, leaving a nested required-adjacent parameter undocumented.

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+resource ('Join a company with an invite join code') and distinguishes it from siblings like invite_member, invite_cofounders, and revoke_invite by framing this as the redemption side of an 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?

Gives clear context: confirm with the user first, prerequisite of authenticated active company access. It does not explicitly name alternatives (e.g. revoke_invite or switch_company) or state when-not to use it, so it stops short of a 5.

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