maya_mesh_operation

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

No annotations provided, so description must disclose behavioral traits. It does not mention whether operations modify the original object, create new ones, require selection, or have undo capabilities. For a mutating tool with multiple operations, this omission is critical.

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?

Single sentence with no filler. Front-loaded with 'Execute mesh operations' and lists operations efficiently. Could include more context without sacrificing conciseness.

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 tool with multiple operation types (some requiring multiple objects), the description lacks behavioral context such as side effects, required object states, or parameter dependencies. Despite an output schema existing, the minimal description is insufficient for complex use cases.

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 provides detailed descriptions for each parameter (e.g., faces, offset, divisions). The description adds a high-level list of operations but does not explain parameter relationships or usage beyond the schema. Schema coverage is high, so baseline 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 the tool executes mesh operations and lists specific types (extrude, bevel, boolean, etc.). It distinguishes from sibling tools like maya_create_primitive (creation) and maya_transform (transformations), but does not explicitly name the resource (e.g., 'on a mesh object').

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 on when to use this tool versus alternatives. Does not specify prerequisites (e.g., object must exist) or provide when-not-to-use scenarios. Sibling tools like maya_create_primitive are for creation, but no explicit comparison.

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