dmm_fetch

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 explicitly discloses the absence of a side-effect (no new trigger), which is the most important behavioral trait for an agent to know. It does not cover edge cases like behavior when no measurement exists, but for a zero-parameter fetch tool the core behavior is well conveyed.

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?

A single, front-loaded sentence that communicates both the action and the critical non-triggering behavior. Every word earns its place, with no redundant detail.

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 tool with an output schema, the description provides all essential information needed to select and invoke it correctly. The distinguishing behavior is stated, and there are no hidden inputs or setup requirements to document.

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 tool has zero parameters, and the input schema is empty, so there is nothing for the description to document. The baseline of 4 applies because the description does not need to compensate for any undocumented 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 states a specific verb ('Fetch'), a specific resource ('the last measurement from the multimeter'), and a key behavioral qualifier ('without triggering a new one'). This clearly distinguishes it from siblings like dmm_read and dmm_measure, which imply a fresh measurement.

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 phrase 'without triggering a new one' gives clear context: this tool is for retrieving an already-acquired measurement rather than initiating acquisition. It does not explicitly name alternative tools or state when not to use them, but the intended usage is clear from the contrast with triggering tools.

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