mesh-subdivide

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It does not state that the operation modifies the mesh, is destructive, or that it affects the active object. It also fails to mention that the 'cuts' parameter controls subdivision levels or that the operation may fail without a selection. This is insufficient transparency for a mutation tool.

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 a single, concise sentence with no superfluous content. It is front-loaded with the essential purpose. Perfectly sized for such a simple operation.

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 the tool's apparent simplicity, the description is incomplete. It lacks details about what 'subdivide' does geometrically, how 'cuts' affects the result, what the 'object' parameter overrides, and what happens if no selection is made. With no output schema and only minimal parameter schemas, the description should provide richer context but does not.

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%, so the description must compensate for explaining the parameters. It does not mention 'cuts' or 'object' at all. While the schema titles ('Number of cuts' and 'Mesh object to edit (defaults to active)') are descriptive, the tool description adds no additional meaning, leaving the parameters under-explained especially regarding their optionality and defaults.

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 states a clear action ('Subdivide') and a specific target ('selected edges/faces'), making the tool's purpose understandable. However, it does not explicitly differentiate itself from similar mesh editing operations like bevel or inset, though the verb 'subdivide' is distinct enough. It is specific but lacks mention of the mesh object context.

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 provides no guidance on when to use this tool versus alternatives. It does not mention typical use cases (e.g., increasing geometry density), prerequisites (like having a selection), or scenarios where other mesh tools would be more appropriate. There is no 'when not to use' or reference to sibling tools.

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