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

Annotations already indicate this is a non-read-only, non-destructive, closed-world mutation. The description adds valuable behavioral context beyond that: owner-only authorization, revocability through allow=false, and the fact that invites remain single-use. It does not clarify whether revoking affects already-issued invites, but it meaningfully supplements the annotation profile.

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?

Two tight sentences with no filler. The owner-only constraint is front-loaded, and the allow=false revoke case is stated immediately after the grant case.

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 permission-mutation tool with annotations, full schema coverage, and no output schema, the description covers the main prerequisites and side effects. A minor gap is that it does not state what happens to already-created invites when permission is revoked.

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%, and the schema already documents workspace_id, agent_id, api_token, and especially allow. The description reinforces allow=false as revocation, but adds little parameter syntax or semantics beyond what the schema already provides.

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 a specific permission-toggle action: letting a member create invites to a private workspace, or revoking that ability with allow=false. It is distinguishable from siblings like create_invite or list_invites because it governs a member's permission rather than creating or listing invites, though it does not explicitly name those sibling tools.

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 gives a clear usage context and prerequisite: 'Owner only' and either granting or revoking permission via allow. It does not explicitly state when to prefer create_invite or invite_by_email instead, so there is no full alternative-routing guidance.

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