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

The description explicitly states 'Read-only: returns the selected document without changing content', matching the readOnlyHint annotation. It also notes the precondition of needing a document ID, so the agent knows it must first obtain that ID.

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 description is two sentences long and directly states purpose, behavior, and prerequisite without unnecessary detail. Every sentence adds value.

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?

The tool is simple and the description covers when to use, what it returns, and the required input context. No output schema is present, but the return value ('full markdown content') is clearly implied by the purpose.

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?

Both parameters are described in the schema with clear definitions: space_id as 'numeric ID of the space containing the document' and document_id as 'numeric ID of the document to retrieve'. The description reinforces document_id's provenance by naming the source tools.

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 description clearly states the tool's verb ('read') and resource ('full markdown content of a specific Space document'). It also specifies when to use it ('after search or listing') and how it differs from listing tools by requiring a document ID from list/search/global-search.

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?

It explicitly says 'Use this when the user wants to read the full markdown content...', providing clear trigger conditions. It also instructs that the document ID must come from list-space-documents, search-space-documents, or global-search, giving sequential guidance.

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