list_collections

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

With no annotations and a description that only repeats the name, the tool's behavior is completely undisclosed. There is no mention of what it returns, side effects, or any restrictions. The description fails its role as the primary source of behavioral information.

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 extremely short, but it is under-specified rather than concise. It adds no value beyond the tool name, so it does not earn its place. The structure provides no front-loaded information that helps an agent.

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?

Despite having an output schema, the description gives no indication of what the tool returns or how it fits into the broader workflow. For a tool that lists collections, the agent has no idea what to expect or how to use the result. The description is functionally blank.

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 the schema is empty and there is nothing for the description to clarify. The baseline of 4 applies since no parameter explanations are required, though the description also fails to provide any contextual meaning. Given the absence of parameters, this is the most generous score justified.

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 'Blender Studio Pro MCP: list_collections' merely restates the tool name with a product prefix. It does not state that the tool lists collections in Blender or specify any action, making it a tautology that offers no functional clarity.

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 guidance on when to use this tool versus alternatives like 'create_collection_hierarchy' or 'list_data_items'. No context, prerequisites, or selection criteria are provided.

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