rhino_mirror

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

Annotations indicate readOnlyHint=false, so mutation is expected. Description adds that by default it creates copies, but does not clarify what happens when make_copy is false (e.g., moving objects) or any permissions needed.

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?

Very short and to the point, but could include more useful information without being verbose. Current length is acceptable but incomplete.

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?

Tool has multiple parameters, nested objects (PlaneModel), and an output schema not shown. Description does not explain how to specify the plane, document context, or object selection. Lacks completeness for a transformation tool.

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?

Description only mentions 'plane' and 'copies by default', ignoring parameters like object_ids, doc_id, and make_copy. Schema description coverage is 0%, so description should compensate but fails to cover most parameters.

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?

Description clearly states the tool mirrors objects across a plane, with default behavior of copying. It provides a specific verb and resource, but does not explicitly differentiate from siblings like rhino_move or rhino_rotate.

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 (e.g., rhino_move, rhino_scale). No prerequisites or conditions mentioned.

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