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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description still adds genuine behavioral context beyond them: which fields come back (tags, lock state, region, recording/transcription settings) and the warning that a space's url is a way in and should be treated as sensitive. It does not mention pagination limits or result-volume expectations.

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 plus the endpoint path, with the core purpose front-loaded before the sensitivity note. The dense comma-run of nine return fields is slightly listy but each item earns its place and there is no filler.

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?

There is no output schema, so spelling out the returned field set is valuable compensation and it is done here. Combined with annotations covering safety and a fully documented parameter schema, an agent has enough to call this correctly; only usage routing among the sibling list tools is absent.

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 every one of the 9 parameters is documented in-schema (including the tag_key/tag_value pairing and the date_after/date_before overlap note). The description adds no parameter-level meaning beyond that, so the baseline of 3 applies; the fields it lists are return values, not inputs.

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 verb and resource ('List the organisation's spaces') and even defines the resource ('persistent rooms'), then enumerates the fields returned. It is clearly the list-spaces tool rather than a session tool, but it never names the adjacent siblings (lessonspace_list_sessions vs lessonspace_list_space_sessions) that an agent could confuse it with.

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?

No explicit when-to-use or when-not-to-use guidance and no named alternative is given. Usage is only implied by the schema's optional filters (search, tag_key, date_after, etc.), which lets a reader infer that this is an unfiltered-with-optional-narrowing list.

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