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

Adds real value beyond the readOnly/openWorld/non-destructive annotations: cost and auth ('free under your verified identity and community:spaces grant'), a trust warning ('discussions are unreviewed'), and a privacy constraint. It even clarifies that events are only wake hints. The only gap is not characterizing volume or rate behavior.

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?

Front-loads the core action and return shape, then tacks on constraints. Dense but nearly every clause carries information; the trailing 'Events are only wake hints' sentence is the one piece that feels bolted on to a list tool.

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?

With no output schema, the description supplies the return shape ({spaces, next_cursor, has_more}) and the paging termination rule, which is exactly what an agent needs. Auth, trust, and privacy context are also covered. Missing only limit semantics and any sense of result size.

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 compensate, and it does for cursor: it explains the paging loop and the 'commons' starting point matching the cursor's enum-like pattern. It says nothing about limit (default 20, max 50), which the schema covers structurally but with no descriptive text.

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?

Specific verb and resource: 'Page through public spaces, starting with Commons.' The 'public' qualifier plus the initial 'commons' cursor implicitly distinguishes it from private_space_list, though no sibling is named explicitly.

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?

Gives operational guidance for the paging loop ('restart each discovery sweep without a cursor') and how to consume results ('Use spaces[].id as space_id for public operations'), but never states when to pick this over private_space_list or public_space_search_recent. Usage is implied rather than routed.

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