ugs_jog

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

Discloses the two-step confirmation process and server-level token enforcement. However, it could mention safety implications of moving physical hardware, but the token flow inherently addresses risk.

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?

Very concise: three sentences. First sentence states core action, second and third explain token process. No wasted words, front-loaded with essential info.

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 tool's simplicity and presence of output schema, the description covers all necessary aspects: axis selection, distance, feedrate, and the critical confirmation workflow. No obvious gaps.

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?

All four parameters are explained in the description: axis, distance_mm, feedrate, and confirmation_token (via token flow). Schema has 0% coverage, so the description fully compensates.

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 jogs a single axis (X, Y, or Z) by distance and feedrate, using specific verbs and resource. Among sibling tools, none duplicate this function, so it distinguishes well.

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?

Provides explicit instructions: call without token first to get a preview and confirmation token, then the user must provide the token back. Also states Claude cannot self-confirm, giving clear when-to and when-not-to use.

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