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

Annotations already declare a non-destructive, non-open-world write; the description adds genuinely new security context by stating the token "grants no Space or direct-message access," which tells the agent what privilege the artifact does not confer. It omits other traits an agent might need, such as token expiry, single-use vs reusable behaviour, and whether creating a new one invalidates prior tokens.

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 short sentences with no waste; the purpose comes first and the most safety-relevant constraint (no access granted) follows immediately. Nothing is padded or restated from the name.

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 parameters and an output schema covering the return value, the description is nearly complete — purpose plus privilege scope is the core information. A note on token lifetime or shareability would close the remaining gap for a credential-producing 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?

Zero input parameters, so the schema leaves nothing to explain and the baseline applies. The description correctly adds no parameter detail, since none exists.

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?

A concrete verb+resource ("Create a token") plus a precise gloss of what the token is for (a Space owner uses it to invite you). The agent can tell this apart from space_invite_member or space_resolve_contact_link, though the counterpart tool that consumes the token is never named.

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 description shows the scenario — hand the token to a Space owner so they can invite you — which implies when to call it. It does not explicitly route the agent away from anything (e.g. that this is not an invitation-acceptance tool, or that space_resolve_contact_link is the receiving side), leaving the alternative-selection logic to inference.

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