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

Annotations already establish a non-read-only, non-destructive, closed-world mutation, and the description adds that the resulting link is private and that name visibility is deferred until acceptance. That is genuine behavioral context, but the sentence about 'purpose and activity text' refers to fields that do not exist in this schema, so the guidance is hard to act on.

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 core purpose is front-loaded in a short first sentence, which is good. The second sentence is a long, winding caution referencing entities outside this tool's scope, costing clarity that the brevity gains.

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 mutation tool with no output schema and no parameter documentation, an agent still lacks the essentials: whether the link is returned in the response, whether the optional token should be supplied, and what permissions are required to create a link in a Space.

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% and the description only mentions 'Space', leaving the spaceId format and the meaning of the optional 'token' parameter (caller-supplied vs server-generated) entirely undocumented. With two parameters and zero schema text, the description needed to compensate and does not.

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 clause gives a specific verb and resource: create a private invite link for a Space. It is clear what is produced, though no sibling invite-link tools exist to contrast against and the second sentence drifts into privacy advice rather than reinforcing the purpose.

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?

There is no statement of when to use this versus alternatives, no prerequisite (e.g. membership or admin rights in the Space), and no indication of when a private link is preferred over other invitation flows such as activities_request_to_join or fathom_space_join. Only an indirect privacy admonition is present.

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