acquire_analog_voltage

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds the finite/bounded transaction nature and the return type (statistics + preview), which are useful, but does not discuss permissions, error behavior, or side effects beyond what annotations cover.

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 a single sentence with no filler. It front-loads the action and concisely states the scope and return.

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?

The tool has 10 parameters, an output schema, and annotations, but the description is minimal. It lacks usage guidance, parameter explanations, and any context about measurement setup, making it under-specified for a tool of this complexity despite the output schema covering return values.

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 does not mention or explain any of the 10 parameters. With schema description coverage at 0%, the burden is on the description to compensate, but it only provides high-level context about the transaction type, leaving parameter semantics (e.g., sample_count vs duration_seconds, trigger_source) unexplained.

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 performs one finite analog-voltage input transaction and returns statistics plus a preview. It distinguishes from sibling record_analog_voltage by emphasizing the finite/bounded nature.

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 use for a single bounded acquisition but does not explicitly compare to alternatives like record_analog_voltage or state when not to use it. No when-to-use or exclusions are provided.

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