new_blend

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

With no annotations provided, the description carries the full burden of disclosing behavior. It offers nothing about side effects, required permissions, state changes, or return values. An agent cannot predict whether this tool is destructive, read-only, or requires a specific Blender state.

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 this is under-specification, not genuine conciseness. It is a redundant restatement of the name, with no useful content. A concise description would still convey purpose; this one conveys nothing beyond the identifier.

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?

Even for a tool with just one optional parameter and an output schema, the description is entirely inadequate. It does not explain the tool's function, when to call it, what it returns, or any prerequisites. The agent is left with no actionable knowledge to invoke it correctly.

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 input schema includes one parameter, 'reset_ui', with a default but no description (schema coverage 0%). The tool description does not mention or explain this parameter at all. Since the schema provides no meaning and the description fails to compensate, the agent cannot interpret what 'reset_ui' does or when to set it.

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: new_blend' is a pure tautology, restating the tool name with a prefix. It gives no verb, resource, or action, so an agent cannot infer what the tool does or how it differs from siblings like create_object or save_blend.

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 zero guidance on when to use this tool, what scenarios it applies to, or exclusions/alternatives. The description contains no contextual cues at all, leaving the agent without any basis for selecting this over other tools.

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