get_acc_hardware

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

No annotations are provided, so the description carries the full burden. It only states the operation (get) and mentions 'Force' and 'AUTO-detect', but does not disclose side effects, read-only nature, or any other behavioral traits. The description adds minimal behavioral context beyond the name.

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 very concise at 16 words, conveying the essential idea. However, it includes type info in brackets that may be more appropriate for output documentation, but the brevity is still effective.

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?

Given no parameters, no annotations, and no output schema, the description is too minimal. It does not explain possible values or the meaning of the returned setting, making it incomplete for an agent to fully understand the tool's behavior.

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 input schema has no parameters, so the baseline is 4. The description mentions '[UINT8, default: AUTO]', which likely describes the output value type, not a parameter. This is acceptable as there are no parameters to document.

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 'Get' and resource 'acc_hardware', indicating retrieving accelerometer hardware selection. It mentions 'Force accelerometer driver or AUTO-detect', which conveys the purpose. However, it does not explain what 'acc_hardware' represents (accelerometer driver selection), slightly reducing clarity.

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 provides no explicit guidance on when to use this tool versus alternatives like set_acc_hardware or calibrate_accelerometer. It only mentions the default value and type, which is insufficient for distinguishing usage context.

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