place_footprint

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

Annotations indicate a non-destructive write, but the description adds no extra behavioral info (e.g., whether it overwrites existing footprints, requires library, or triggers automatic saves). Does not clarify idempotency or side effects.

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?

Single paragraph with a clear 'Args:' list. Every sentence is useful, front-loaded with purpose. No redundant text.

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?

Output schema exists but is not shown; description doesn't explain return value. For a tool with 7 parameters and potential side effects on PCB file, more context on behavior and failure modes would be helpful. Parameter descriptions are complete within their scope.

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 coverage is 0%, but description provides examples and units for each parameter (e.g., 'Reference designator (e.g. "R2")', 'X position in mm'). Adds meaning beyond schema title, though constraints like rotation range are omitted.

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 the action ('Place a footprint on the PCB') and the resource (footprint on PCB). It distinguishes among siblings like 'move_footprint' and 'remove_footprint' by specifying a placement action.

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 vs alternatives (e.g., 'place_component' in schematic, 'move_footprint'). No prerequisites or when-not-to-use instructions given.

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