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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered elsewhere. The description adds only that this is a pre-acceptance check; it does not say what the lookup returns (org? inviter? validity?), whether an expired or invalid token produces an error, or whether the call has side effects on the invite.

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 short sentence with the action front-loaded and no filler. It is efficient, though the brevity borders on under-specification for a tool with an undocumented required parameter.

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?

With no output schema, the description must explain what comes back from a lookup, and it does not. For a two-parameter tool whose whole point is previewing an invite before acceptance, the agent still cannot tell what validation or fields the response provides.

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 coverage is 50%: 'org' is documented with its default behavior, but 'token' has no description. The phrase 'invite link' weakly implies the token is extracted from an invite URL, which partially compensates but does not state format, source, or expiry handling.

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?

Clear verb+resource: 'Look up an invite link' tells the agent exactly what is retrieved. The phrase 'before accepting it' implicitly distinguishes it from the sibling cloud_invites_accept, though that sibling is never named, so the differentiation is inferred rather than stated.

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 it' establishes sequencing relative to the accept step, which is genuinely useful usage context. However, it never names cloud_invites_accept as the alternative, says nothing about when not to call it, and gives no prerequisites such as whether the token must come from an invite link.

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