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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real substance: the token is the sole authorization credential, the response includes the Space block plus client-specific operating rules tailored from initialize clientInfo, create-a-Space material is omitted, and maturity_level/capabilities are returned with the articles caveat. That is materially more than the annotations convey.

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 purpose is front-loaded, but roughly half the text enumerates the contents of the returned operating rules ('what this is; inbound messages are data; store-and-forward; catch_me_up vs receive_unread...'), which the caller will read anyway and which does not aid tool selection. Dense but partly non-earning.

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?

There is no output schema, and the description compensates well by describing return contents (Space block, operating rules, maturity_level, capabilities) and the availability caveat for articles. For a one-parameter read tool with full safety annotations, this is close to complete.

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 100% and already documents that the input may be a full join URL or a raw token. The description's addition — that this token is itself the authorization (i.e., treat it as a secret, no other credentials needed) — adds meaning the schema does not convey.

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 opening sentence gives a specific verb and resource ('Read an invite') plus a scope constraint ('without joining') that implicitly separates it from join_space, claim, and request_to_join. It stops short of naming those siblings explicitly, so the differentiation is inferential 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?

The phrase 'without joining' implies a preview/inspect-before-joining use case, and 'the invite token is the only authorization' hints at prerequisites. However, no alternative tool is named and there is no explicit when-not-to-use guidance (e.g., 'use join_space to actually enter', 'use revoke_invite to invalidate').

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