gcode_run_macro

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

With no annotations, the description fully discloses the two-step confirmation process, the token mechanism at server level, and the safety check. It covers what happens (preview, confirmation needed) without concealing any behavior.

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?

Four sentences, each necessary. No redundancy, front-loaded with the primary action. Efficiently communicates workflow, constraints, and rationale.

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?

Given two parameters, an output schema (not shown but exists), and no annotations, the description covers the workflow and safety. Could be slightly more complete by noting output format or error cases, but the output schema likely covers that.

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 description coverage is 0%, but the description adds meaning: 'name' is the macro to run, and 'confirmation_token' is explained as the token from the first call. It correctly implies the token is optional initially. However, it could be more explicit about the default value behavior.

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 'Run a saved macro by name' - a specific verb ('Run') and resource ('saved macro') with scope. It distinguishes from sibling tools (e.g., gcode_save_macro, gcode_list_macros) by focusing on execution.

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?

Explicit step-by-step usage: call with no token first to get preview/safety check/token, then user must provide token back. Also states 'Claude CANNOT self-confirm', which is critical guidance for proper invocation.

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