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

With no annotations, the description carries the full burden and does add two facts: it is admin-restricted and the invite link is invalidated. However, it omits whether the revocation is reversible, what happens to any existing member state, and how errors (already-accepted or expired invite) are surfaced for a mutation tool.

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?

A single efficient sentence, front-loaded with the audience ('Admins:') and the action. Nothing is wasted, though the terse format leaves little room for the guidance the low-coverage schema needs.

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 two-param mutation with no annotations and no output schema, the description covers the role requirement and the outcome but leaves parameter meaning and reversibility unexplained. It is minimally adequate but has clear gaps given the structured data provides no support.

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 both required params. The phrase 'by id' loosely maps to the 'id' parameter but adds no format or scope detail, and the required 'workspaceId' parameter is never mentioned or explained in the description.

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 (revoke) and resource (a pending member invitation), plus the effect ('link stops working'). This usefully distinguishes it from members_remove (removing an existing member), though it does not clarify its relationship to the near-identical invitations_revoke 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 'Admins:' prefix implies a permission prerequisite, but there is no explicit when-to-use vs alternatives guidance. It never tells the agent to prefer this over members_remove or invitations_revoke, nor what condition (a pending, unaccepted invite) should route here.

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