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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the description adds marginal value by reiterating 'read-only' and 'without changing content.' It does explicitly mention what the tool returns (documents and folders), which is useful. For a simple read operation with no side effects, this level of transparency is sufficient. No contradiction with annotations.

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 with no fluff. The primary usage guidance is front-loaded, and the read-only constraint is stated concisely. Every sentence adds value and no information is redundant beyond the annotations.

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 tool with one simple parameter, no output schema, and clear annotations, the description covers the essential context: when to use, what it does, and what it returns (documents and folders). It doesn't mention pagination or limits, but given the simplicity and the fact that no output schema exists, the level of detail is adequate for an agent to invoke correctly.

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 100%, and the parameter description already explains space_id as a numeric ID and directs to call list-spaces first. The tool description adds 'one numeric space_id' which reinforces the single-value requirement but doesn't add new semantic details. The schema carries the explanatory load, so the baseline of 3 applies.

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 states a specific set of actions (browse, list, find IDs, inspect structure) on a specific resource (Space tree, documents, folders) and explicitly notes it is read-only. It clearly distinguishes from search-space-documents (which implies search semantics) and get-space-document (single document retrieval) by covering the full tree browsing use case.

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 says exactly when to use: browsing a Space tree, listing documents, finding numeric IDs, inspecting structure before editing. It also adds the condition 'for one numeric space_id' and implies a prerequisite (call list-spaces first) via the parameter description. It doesn't explicitly name alternatives or exclusions, but the use cases are well-defined.

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