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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower, and the description adds genuinely useful context by enumerating the returned fields (id, name, people, flows, linked folders, sidebar count, last-moved). It does not mention pagination, limits, or ordering, but with no annotations gap to fill this is solid.

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 resource definition, then returns, then routing guidance, in three tight sentences. The 'where groups of people work together with zv1 and flows' clause is mild flavor but sets context cheaply.

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 appropriately compensates by listing the return fields and stating the tool's role in the room workflow. Nothing critical for correct invocation is missing, though pagination/ordering behavior is unstated.

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%, with both workspace and includeArchived well documented in the schema itself, so baseline is 3. The description adds nothing about either parameter beyond what the schema provides.

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?

States a specific verb and resource ('The workspace's rooms') and clearly positions the tool among siblings by naming what it returns and how it relates to rooms_read and rooms_post. An agent can distinguish it from those siblings without opening the schema.

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?

Explicitly tells the agent when to use it ('to find the room a user means before rooms_read or rooms_post'), naming the alternatives and the selecting condition. No explicit when-not or exclusion is given, but the routing intent is clear.

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