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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that the old invite is revoked, a new one is created with the same email and role, the new link works once for 14 days, only owners/office can use it, and accepted/revoked invites are refused.

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 front-loaded with the core action and then layers on the most important behavioral details in a compact sequence. Every sentence adds distinct, useful information without repetition.

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?

Given no annotations, an output schema, and one parameter, the description thoroughly covers side effects, permissions, constraints, and token lifetime. The main gap is that it does not clarify the required input invite_id parameter, which matters because schema coverage is 0%.

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% and the single required parameter invite_id is not explained. The description mentions "use the invite_id this returns from now on," which refers to the output rather than clarifying that the input invite_id should be the old invite's identifier. The parameter's meaning is left ambiguous.

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 ("Email an open invite again") and resource (open invite), and clarifies it is for a worker or office member who lost or expired their invite. This clearly distinguishes it from members_invite, which would create a new invite rather than resend an existing one.

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?

It provides clear conditions for use (lost/expired invite, worker or office member) and exclusions (owners/office only, accepted or revoked invites refused). It does not explicitly name the sibling alternative members_invite, but the context is strong enough for an agent to choose correctly.

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