list_collections

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

The readOnlyHint annotation already covers the safety profile, and the description confirms this by using 'List' rather than a mutation verb. It adds useful scope ('all' collections), but no further behavioral traits such as performance, permissions, or side effects are disclosed; this is a minor gap for such a simple 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 short, front-loaded sentence conveys the action, resource, and return contents with no filler. Every word contributes to an agent's understanding of what the tool does.

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 zero parameters, an output schema to define the return shape, and a readOnly annotation, the description is sufficient for an agent to select and invoke the tool correctly. The implied 'current scene/file' context is normal for this MCP domain and not a meaningful omission.

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 takes no parameters, so the baseline of 4 applies. There is no parameter meaning for the description to explain, and the schema coverage is trivially complete.

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 opens with the verb 'List' and the resource 'collections', then specifies what kind of data is returned: child counts, object counts, and visibility. This clearly differentiates it from sibling list_* tools such as list_objects and list_materials.

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?

The use case is evident: call this tool when you need an inventory of all collections and their counts/visibility. It does not name alternatives or exclusion conditions, but 'all collections' and the zero-parameter signature provide clear read-only context.

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