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 access constraint (must be a member) and a preview of returned fields, but the output schema already documents return values, leaving little genuinely new behavioral context.

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; the scope constraint and the field summary are stated up front and nothing is redundant.

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 one-parameter read tool with full annotations and an output schema, the description covers purpose, access scope and content. The only gap is not explaining the single required parameter or its source, which is minor given the existing pattern constraint.

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 0%, so the description must carry parameter meaning, yet it never mentions space_id or where to obtain one. The schema's regex pattern conveys the expected format, but the description does not compensate with guidance such as sourcing the ID from space_list.

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?

States a specific verb and resource ('Read a private Space') and enumerates the salient return fields (owner, your role, actor ID). It is clearly distinguishable from space_list, though it never explicitly names that sibling as the alternative for listing.

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?

'A private Space you belong to' implies a membership prerequisite, which is useful usage context. However, it gives no explicit when-to-use/when-not guidance and does not route the agent to space_list, space_get_actor, or space_resolve_contact_link for related lookups.

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