dmm_set_resolution

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says the resolution is set; it does not mention valid values, units, side effects on measurements, persistence, or whether a reset is needed.

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 short and front-loaded, but the Args section is redundant with the schema and does not earn its place. It is concise without being substantively informative.

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 one-parameter setter with no annotations and zero schema coverage, this description is not complete enough. Without documenting what values are valid or what effect resolution has on measurement behavior, an agent cannot safely choose the correct argument.

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 coverage is 0%, yet the description's only parameter guidance is 'resolution: Resolution value,' which is a tautology and adds nothing beyond the schema's number type and title. The agent receives no units, bounds, or acceptable value ranges.

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 a specific action ('Set') and resource ('measurement resolution on the multimeter'), distinguishing it from other DMM tools like dmm_set_range or dmm_set_nplc. It does not define what 'resolution' means in instrument terms, but the core purpose is unambiguous.

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 implies this tool should be used whenever the resolution needs to be configured, and it gives no misleading exclusions. However, it provides no guidance on how resolution relates to range, NPLC, or auto-range alternatives, leaving the agent without a clear selection heuristic.

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