run_kicad_script

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

With no annotations provided, the description carries the full burden of disclosure and does so well: it states that the tool runs arbitrary local code with the user's privileges, explains how print output is captured, and how to return a value via the 'result' variable. It also warns about a known broken import.

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 compact and front-loaded, with every sentence providing necessary information: purpose, usage, environment, return mechanism, and warnings. No filler or redundancy.

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?

Despite having no annotations or output schema, the description sufficiently covers the important behavioral aspects of a fallback script execution tool, including environment, return protocol, and safety considerations. Minor gaps like timeout semantics are partially covered by the schema default.

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 provides context for the `code` parameter by listing available Python names and showing how to return values, but it does not explain the `timeout` parameter at all. With 0% schema description coverage, this gap is not fully 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 tool executes Python with the KiCad API pre-imported, and explicitly frames it as a fallback for anything the curated tools do not cover. The verb 'Execute' and resource 'Python with the KiCad API' are specific and distinguish it from the sibling tools.

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 gives explicit when-to-use guidance: 'Use this for anything the curated tools do not cover,' implying curated tools should be preferred. It also provides a specific exclusion about kipy.schematic, making limitations clear.

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