move_and_rotate_footprint

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

With no annotations provided, the burden falls on the description. It only says 'in one operation' hinting at atomicity but does not disclose key behavioral traits such as coordinate system, units, prerequisites, or what happens on failure.

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 sentence that immediately conveys the tool's purpose without extra words. However, it sacrifices necessary detail for brevity.

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?

Given the tool has 4 parameters, no output schema, and no annotations, the description is severely incomplete. It lacks critical information about parameters, behavior, and return values, leaving an AI agent with insufficient 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?

Schema description coverage is 0%, and the description adds no meaning to the parameters (reference, x_mm, y_mm, rotation_deg). It fails to explain what each parameter represents or how they are used.

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 'Move and rotate a footprint in one operation,' which is a specific verb+resource combination and distinguishes it from sibling tools like move_footprint and rotate_footprint.

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 implies when to use this tool (when both move and rotate are needed) but does not explicitly provide guidance on when not to use it or mention alternatives like separate move/rotate calls.

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