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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful implication that results are membership-scoped (the token must belong to the space), but it never states what happens for a non-member token or whether the view is filtered/redacted, which is the key behavioral question for this tool.

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 no filler. It is efficient, though its terseness borders on under-specification rather than crispness.

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 annotations covering safety and no output schema, the description only needs to explain access behavior and result shape. It gestures at the membership-scoped view but leaves unclear what is actually returned (space metadata vs. activities vs. views) and what happens on authorization failure, which matters for a private-resource read.

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 only 50%: 'token' is documented (including the pointer to fathom_space_join) but 'spaceId' has no schema description at all. The tool description says nothing about either parameter, so it fails to compensate for the undocumented spaceId or to explain the token/membership relationship.

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 sentence pairs a specific verb ('Read') with a specific resource ('a private Space') and adds a scoping qualifier ('as its members see it') that signals a membership-relative projection. It does not, however, distinguish this from near-siblings like fathom_space_context or spaces_get, so an agent cannot route on the description alone.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The word 'private' weakly implies this is not the tool for public spaces (spaces_list_public), but the agent must infer that, and nothing clarifies the boundary with fathom_space_context or spaces_get.

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