load_gcode

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'load' and 'execution', implying a write operation that may start or queue a job, but doesn't clarify if this requires specific machine states, permissions, or has side effects like overwriting existing content. For a tool with potential safety implications in CNC operations, this is a significant gap.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 the complexity of CNC operations and lack of annotations or output schema, the description is incomplete. It doesn't address critical context like error handling, machine state requirements, or what happens after loading (e.g., does execution start automatically?). For a tool in a safety-sensitive domain, this leaves too much undefined.

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 100%, with clear descriptions for both parameters ('name' and 'content'). The description adds no additional meaning beyond the schema, such as format details for G-code or naming conventions. Baseline 3 is appropriate since the schema adequately documents the parameters.

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 ('Load') and target ('G-code content into CNCjs for execution'), which is specific and unambiguous. However, it doesn't distinguish this tool from sibling tools like 'send_gcode' or 'start_job', which might have overlapping or related functionality in the CNCjs context.

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?

The description provides no guidance on when to use this tool versus alternatives like 'send_gcode' or 'start_job'. It lacks context about prerequisites (e.g., whether a connection must be established first) or typical workflows, leaving the agent to infer usage from the tool name alone.

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