kicad.add_power_symbol

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

No annotations provided, so description carries full burden. It discloses that the symbol creates a global net connection, which is key behavioral context. However, it omits mutation safety details (idempotency, error handling if invalid name provided), forcing the agent to infer destructiveness from 'Add'.

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?

Three sentences with zero waste: declaration, behavioral note, and concrete example. Information is front-loaded with the action verb, making it immediately 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?

Adequate for a 4-parameter tool with output schema (so return values needn't be explained), but gaps remain in documenting optional parameters (rotation) and behavioral edge cases. Meets minimum viable standard but lacks richness given zero annotations.

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 has 0% description coverage. The description compensates partially via the example showing name='+3V3', x=100, y=30, clarifying that name is the power net label and x/y are coordinates. However, it fails to document the rotation parameter, coordinate units, or valid name formats.

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?

Clear verb ('Add') and resource ('power symbol') with concrete examples (VCC, GND, +3V3). Distinguishes from generic components via the power-specific examples, though it could explicitly differentiate from add_global_label which also creates global nets.

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?

Provides an example invocation showing syntax, and mentions 'Creates global net connection' implying usage for power distribution. However, lacks explicit guidance on when to use this versus add_global_label or prerequisites like open project/schematic.

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