set_spindle_override

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation ('Adjust') but doesn't specify if this requires specific permissions, whether changes are immediate or reversible, or what happens if the machine is offline. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise—a single, front-loaded sentence that directly states the tool's function without unnecessary words. Every part of the sentence earns its place by specifying the action, resource, and constraints.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like safety, side effects, or response format, leaving significant gaps for the agent to operate effectively in a machine control context.

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 adds minimal value beyond the input schema, which already fully documents the 'value' parameter with its range and description. The description restates the range (10-200%) but doesn't provide additional context like units or effects, resulting in a baseline score due to high schema coverage (100%).

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 ('Adjust') and resource ('spindle speed override') with a specific range (10-200%), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'set_feed_override', which serves a similar function for feed rate rather than spindle speed.

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 is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., machine must be connected or in a certain state) or comparisons to siblings like 'set_feed_override', leaving the agent to infer usage scenarios.

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