set_acc_high_range

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

No annotations provided, so description bears full burden. It discloses the parameter type (UINT8) and default (OFF), but lacks details on side effects, persistence, or error behavior if the sensor does not support high-range mode. Some useful info but incomplete.

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 sentences, no wasted words. First sentence clearly states purpose, second adds parameter info. Efficient and well-structured.

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 simple one-parameter set tool, the description covers purpose and default, but lacks explanation of what high-range mode means, what range of values are valid, and any behavioral notes. Given no output schema and no annotations, it is adequate but not fully complete.

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 provides parameter info but description adds the default value 'OFF' which is not in the schema. It also confirms the type as UINT8. With 100% schema coverage, the description adds meaningful default, enhancing semantics.

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 verb 'Enable' and resource 'high-range accelerometer mode' with a condition 'for sensors that support it'. It is distinct from siblings like get_acc_high_range (read) and calibrate_accelerometer (different action).

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?

No guidance on when to use this tool versus alternatives, no prerequisites, no conditions for use or when not to use. The description does not help the agent decide between set_acc_high_range and other set_ tools.

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