rotate_footprint

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

Discloses 'Single undo step', adding behavioral context beyond the raw action. However, with no annotations, it omits details like required state (e.g., board must be open), error handling, and whether the operation is immediate.

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?

Two concise, front-loaded sentences with no waste. Efficient communication of core functionality.

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?

Minimal but covers the essential action and parameter roles. Lacks details on parameter constraints, expected outcomes, and error scenarios, which is notable given no annotations and no output schema.

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 description implies that 'degrees' is the rotation angle and 'reference' identifies the footprint, but does not specify format for 'reference' (e.g., name, ID). With 0% schema coverage, more detail is needed.

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 'Set' and clearly identifies the resource 'footprint's rotation' and context 'on the live board'. It distinguishes well from siblings like 'move_footprint' and 'duplicate_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?

No explicit guidance on when to use this tool versus alternatives like 'move_footprint'. The description lacks prerequisites or exclusions.

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