get_jog_settings

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose the capability requirement ('state'), which is real value, but says nothing about whether the values are cached/live, what happens if the machine is disconnected, or the return shape.

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?

Two short sentences with no waste. Minor structure issue: the capability prerequisite leads ahead of the actual purpose, so the agent reads a gate condition before learning what the tool does.

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 zero-parameter read-only getter with no output schema, the description covers purpose, unit context, and the access prerequisite. The only gap is the shape of the returned jog settings, which no output schema documents.

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?

Zero parameters, so the baseline is 4. The 'in display units' note adds useful semantics about the values returned, though it speaks to output rather than 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?

States a specific resource and verb: it returns the current jog distance and speed settings, with the added qualifier 'in display units'. It's clear what the tool reads, though it doesn't distinguish itself from siblings like get_units or get_position that touch adjacent state.

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 'Requires capability "state"' clause gives an access precondition, which is useful, but there's no guidance on when to call this versus get_units, get_position, or get_state_snapshot. Usage is implied rather than directed.

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