edit_schematic_place

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

Discloses that the tool uploads the schematic for server-side modification and returns a unified diff for review, providing useful behavioral context beyond the action itself. No annotations present to contradict.

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 sentences: first states core action, second describes mechanism and output. No redundant information, highly efficient.

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?

Mentions output (unified diff) but does not address error cases (e.g., duplicate reference, invalid symbol). With output schema present, description is adequate but not fully comprehensive.

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 100%, so parameters are well-documented in schema. Description does not add extra meaning beyond what schema provides (e.g., coordinate system details). Baseline score applies.

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?

Clearly states the action 'Place a symbol instance' and the resource 'KiCad schematic'. Distinguishes from sibling tools like edit_schematic_remove and edit_schematic_wire by specifying the operation.

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. Does not mention preconditions like file must exist, or when to choose this over other edit tools.

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