apply_symmetry

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

The description doesn't add behavioral details beyond the annotations. While annotations indicate destructiveHint=true, the description merely says 'add modifier' without explaining the actual destructive effect on geometry or that it applies symmetry.

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 short sentence, which is concise but under-specified. It lacks essential details and reads more like an under-specification than an efficient summary.

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?

The tool has 2 parameters, an output schema, and annotations, but the description provides almost none of the necessary context. It fails to clarify the object target, axes behavior, return value, or relationship to sibling tools.

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%, and the description does not explain the parameters 'obj_name' or 'axes'. It does not mention that axes defaults to ['X','Y'] or what values are valid.

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 that the tool adds a Mirror modifier for symmetry, which is a specific action on a resource. However, it does not distinguish itself from the sibling tool 'add_modifier' or mention the target 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 is provided on when to use this tool versus alternatives like add_modifier or apply_modifiers. There is no context about prerequisites or typical use cases.

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