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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond that: results are limited to visible collections, the response is a lean one-entry-per-collection overview, and total_objects is provided to help decide whether to paginate or enumerate.

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?

The description is front-loaded and structured well, moving from what the tool does to return shape and then next-step siblings. It is slightly redundant in enumerating all returned fields despite an output schema, though the total_objects rationale earns its place.

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 an output schema and strong annotations already present, the description supplies the remaining context an agent needs: visibility scope, overview granularity, useful return highlights, and explicit next-tool routing. Nothing critical is missing for a zero-parameter listing tool.

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?

The tool has zero parameters, so there is no parameter semantics burden. The description appropriately does not invent parameter details; the baseline score for a zero-parameter tool 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 states a specific resource and scope: collections visible to the caller, one entry per collection. It explicitly contrasts this lean overview with describe_collection for per-property detail and with query_collection/search_collection/get_object for data, so an agent can distinguish its role from key siblings.

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 gives clear routing guidance: use describe_collection for per-property detail, then query_collection/search_collection/get_object to retrieve data. It does not explicitly state when not to use this tool or how it differs from search_collections, so it is strong but not fully exhaustive.

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