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

The annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is fully covered. The description adds useful context about what the result conveys (purpose, material types, current active status) but says nothing about ordering, pagination, or how the optional visitor_name interacts with this read operation.

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?

One front-loaded sentence with no filler; the enumerated clauses each carry information about the returned fields. Slightly dense at four items in a single sentence but still easy to parse.

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 parameterless read-only listing tool with no output schema and full annotation coverage, the description supplies enough: what the collection entries represent and what attributes accompany each one. Nothing an agent needs in order to call it correctly is missing.

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 single visitor_name parameter is fully documented in the schema, including the note that reading requires no name. The description adds nothing about the parameter, which is acceptable at this coverage level but is a missed opportunity to confirm the name is irrelevant here.

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?

"List the collections the live search queries" gives a specific verb and resource, and the enumeration of what each entry covers (purpose, material types, active status) makes the return shape concrete. It does not name or distinguish itself from the sibling tools list_open_collections and search_open_collections, so an agent must infer the difference from the word "live" alone.

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?

There is no when-to-use guidance and no exclusions. Given three sibling tools with overlapping collection-listing semantics (list_open_collections, search_open_collections, list_open_rooms), the description leaves the agent to guess which one answers a given query.

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