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

No annotations provided, so the description carries full behavioral burden. It discloses 'Public', a useful hint that no authentication is required, and 'show' implies read-only. However it omits whether the token is secret-sensitive, error behavior on invalid tokens, or idempotency.

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 front-loaded sentence with zero filler; the scope, the returned fields, and the 'before accepting' cue all earn their place.

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?

No output schema exists, and the description usefully enumerates the returned fields (workspace, inviter, role, invited email, status), which compensates well. The only gap is deeper token-handling detail, which matters little for a one-parameter preview tool.

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?

One token parameter at 0% schema coverage, so the description must compensate. 'Invitation link' implies the token is the invitation token, but it gives no format, length, or invalid-token behavior beyond what the field name suggests.

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 (show) and resource (what a member invitation link grants) plus the exact fields returned. It implicitly contrasts with members_accept via 'before accepting', though it does not name that sibling explicitly.

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?

'before accepting' gives clear usage context and routes the agent relative to the accept flow, implying this is the inspection step that precedes members_accept. No explicit when-not-to-use guidance, but the timing cue is strong.

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