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 reinforces this ('Read-only... without changing content') and clarifies the scope is one space, but adds little beyond what annotations provide and says nothing about pagination or result volume.

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, front-loaded with the 'Use this when...' trigger clause and followed by the read-only scoping caveat. No filler, though the read-only statement is mildly redundant with 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 one-parameter, read-only listing tool with no output schema, the description covers trigger, scope, and side-effect profile adequately. The only gap is the absence of routing guidance against search-space-documents, which would help an agent choose 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 coverage is 100% and the single parameter is already documented, including the 'Call list-spaces first' prerequisite. The description only restates that it is one numeric space_id, adding no format or constraint detail beyond the schema. Baseline 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 gives a specific verb ('list/browse') and resource ('documents and folders in a Space tree'), and scopes it to a single numeric space_id. It does not name the closest siblings (search-space-documents, get-space-document) to sharpen the boundary, but the intent is unambiguous.

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 states clear trigger conditions: browsing a Space tree, listing pages/docs/folders, finding numeric IDs, or inspecting structure before editing. It stops short of naming alternatives (e.g. use search-space-documents for keyword lookup) or stating when not to use it, so it falls short of a 5.

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