run_kicad_action

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

No annotations provided, so description must disclose behavior. Only 'unstable API' is mentioned, hinting at potential instability but no details on side effects, permissions, or return behavior. Does not indicate whether the action is read-only or destructive.

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 sentence is concise and front-loaded, but lacks necessary detail. Could benefit from more context without becoming verbose.

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?

With one required parameter and no enum constraints, description fails to explain valid action names or how to discover them. Sibling tools like search_tools might help but are not referenced. Output schema exists but unknown.

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?

Input schema has 0% description coverage for the only parameter 'action'. Description adds 'by name', implying the parameter is an action name, but no examples, enum, or format details. Output schema exists but is not provided, so cannot compensate.

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?

Description clearly states the tool runs a KiCad editor action by name, specifying the verb and resource. It distinguishes from similar tools like execute_kicad_tool by mentioning 'action' versus 'tool', though the distinction is not elaborated.

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 like execute_kicad_tool. The only hint is 'unstable API', which warns but does not help with selection. Sibling tools list does not clarify usage context.

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