move_footprint

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action and does not mention side effects, required permissions, coordinate system, or what happens to the original footprint (e.g., moved or copied).

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 (9 words), which is concise but at the expense of necessary detail. It could be expanded with parameter explanations and usage context while remaining brief.

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 three required parameters with no schema descriptions and no annotations, the description is insufficient. It does not explain how to use the parameters or the behavior of the move operation. The presence of an output schema offsets the need for return value details, but the description still lacks completeness.

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 has 0% description coverage, leaving three parameters (reference, x, y) completely unexplained. The description adds no meaning beyond the parameter names. For example, it does not clarify the format of 'reference' (ID, name, or position) or the units of x and y.

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 states 'Move a footprint to a new position by reference,' which clearly identifies the action (move), resource (footprint), and mechanism (by reference). However, it does not distinguish itself from the sibling tool 'move_item,' which may share similar functionality.

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 provides no guidance on when to use this tool versus alternatives like 'move_item' or 'rotate_footprint.' It does not specify prerequisites, such as whether the footprint must be selected or if a specific reference format is required.

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