sch_place_component

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

With no annotations, the description carries full burden. It mentions 'Place', implying mutation, but does not disclose any behavioral traits such as side effects, permissions needed, or handling of overlapping components. The description is insufficient for understanding the tool's impact.

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 two sentences, front-loaded with the action, and contains no unnecessary words. It earn its place by providing key usage information efficiently.

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?

For a tool with 10 parameters, no output schema, and no annotations, the description is too brief. It does not explain the effect on the schematic, return behavior, or how to handle multiple placements, leaving significant gaps for an AI agent.

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 50%, and the description adds context for uuid and libraryUuid (e.g., origin from sch_search_component, use of 'lcsc'). However, it does not explain other parameters like mirror, rotation, addIntoBom, addIntoPcb, or subPartName, leaving gaps partially compensated.

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 schematic component from a library at a position' and distinguishes it from sibling tools like sch_search_component (search) and sch_delete_components (delete). It also provides a specific verb+resource pairing.

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?

It explicitly says to provide uuid and libraryUuid from sch_search_component, giving a clear prerequisite. It also notes the special case of libraryUuid 'lcsc' for online placement. However, it does not discuss when not to use this tool or mention alternatives.

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