instance_collection

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

Annotations are absent, so the description bears full responsibility for disclosing behavior (e.g., side effects, permissions, return types). It provides none. There is no mention of what 'instance_collection' does, what it affects, or what the output schema contains.

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?

While the text is extremely short, this is under-specification rather than conciseness. It is a single fragment that does not earn its place; it merely labels the tool without adding information.

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?

Given the tool's complexity (3 parameters, a required one, and an output schema), the description is completely inadequate. It lacks all necessary context: what the tool does, when to use it, how parameters are used, and what the output represents. The presence of an output schema does not compensate for the total absence of semantic content.

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 0% for the three parameters (name, location, collection_name), and the description does not elaborate on any of them. Required parameter collection_name is undefined, and optional parameters have no meaning explained. The description adds zero semantic value.

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 is only 'Blender Studio Pro MCP: instance_collection', which repeats the tool name without any verb or resource explanation. It does not state what action the tool performs, so an agent cannot infer its purpose from the text 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?

No guidance is provided on when to use this tool versus its siblings (e.g., create_collection, move_to_collection). The description gives no context, prerequisites, or examples, leaving the agent without any decision-making basis.

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