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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the 'read-only, does not change content' sentence is partly redundant. However, the description adds real value by naming the return payload ('full markdown content') and the upstream prerequisite chain for the document ID. It does not discuss size limits or pagination for large documents.

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 tight sentences with zero filler, and the use case is front-loaded before the prerequisite. Every clause carries information.

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 two-parameter read tool with no output schema and full annotation coverage, the definition covers trigger, safety, return content type, and prerequisites. The only gap is behavior for very large documents or missing/invalid IDs.

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%, so both parameters are already documented in the schema (including the space_id note to call list-spaces first). The description adds only provenance for document_id, and never mentions space_id at all, so it does not exceed the schema baseline.

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 the full markdown content of a specific Space document/page. It also distinguishes itself from the discovery siblings (list-space-documents, search-space-documents, global-search), which only locate documents rather than returning content.

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?

Explicitly states the triggering condition ('after search or listing') and names the three tools that supply the required document ID. An agent knows exactly when to reach for this tool and what must happen before it.

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