blender_mesh_inset

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

No annotations are provided, so the description carries the full burden of explaining behavioral traits. It says the tool insets faces, but it does not disclose that this modifies the mesh in place, whether it affects face selection, or any prerequisites or side effects. For a mutating geometry tool, this leaves notable behavioral gaps.

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 two sentences with no filler. The core action is front-loaded, and the second sentence adds practical use-case value rather than redundancy. Every sentence earns its place.

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 6-parameter mesh editing tool with no annotations and no output schema, the description covers the essential purpose and typical applications. However, it lacks guidance on selecting it over similar mesh tools and does not disclose behavioral side effects, leaving the definition only minimally complete.

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 100%, so the input schema already documents all six parameters thoroughly. The description adds no parameter-level detail beyond the schema, but with full coverage the baseline of 3 is appropriate.

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 clearly states a specific verb and resource: 'Inset faces to create border loops.' It also names concrete use cases like panel lines and window frames, which helps an agent identify when this tool is relevant. It does not explicitly distinguish itself from sibling mesh tools like bevel or loop cut, so it falls short of a 5.

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 description gives practical context for when to use the tool: 'Essential for panel lines, window frames, recessed details on hard surfaces.' This is clear use-case guidance, but it does not mention alternatives or when not to use inset versus bevel, extrude, or loop cut, so it is not fully explicit about exclusions.

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