extrude_region

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

With no annotations, the description carries the full burden of disclosing behavior. It gives no indication that this operation likely modifies a mesh (e.g., extrudes faces or edges), what happens to existing geometry, whether it is destructive, or what the output will be. The description is essentially empty.

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 rather than effective conciseness. There is no useful structure or front-loaded information beyond the tool name.

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?

For a mesh-editing operation in a complex 3D tool, this description is completely inadequate. It lacks any explanation of prerequisites, effect, parameter meaning, or return value, and no annotations or rich output schema compensate for the absence of information.

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 defines a single 'value' parameter with a default but no description, and schema description coverage is 0%. The description does not explain what 'value' means (e.g., extrusion amount, offset, distance). The tool is severely under-documented for its only parameter.

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: extrude_region' merely restates the tool name without specifying what the operation does, what geometry it operates on, or how it differs from sibling tools. It is a pure tautology.

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 the many other mesh manipulation tools (e.g., subdivide, bevel, inset_faces). There is no mention of prerequisites, selection requirements, or when alternatives are more appropriate.

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