revert_local_orientation

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

Annotations provide only false flags, so they do not convey safety or effect. The description does not disclose whether the operation permanently modifies elements, overrides user-defined orientation values, or is reversible, leaving behavioral impact unclear 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 entry is compact and front-loads the action in its first sentence, followed by the args. The Chinese translation duplicates the English text, adding some redundancy, but the overall structure remains tight and scannable.

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 is low-complexity with a single parameter and no output schema, so the description covers the basics. It remains incomplete around when to apply the tool and what side effects to expect, which is notable given the annotations provide no behavioral context.

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 schema provides zero description coverage for 'ids', so the description's 'Element ID(s) to revert' is the only semantic information. It clarifies the parameter's role and allows a list, though it does not specify type or accepted format.

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 uses a specific verb ('revert') and noun phrase ('local orientation of frame elements'), clearly identifying the action and resource. It is distinguishable from sibling tools like update_element_beta, though it does not explicitly explain what 'revert' entails relative to those alternatives.

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; there are no prerequisites, exclusions, or references to sibling tools. The description only restates the operation and parameter, leaving the agent to infer the appropriate usage context.

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