get_acc_calibration

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 discloses that the offsets are written by the calibration routine and should not be manually edited, which is useful context for a getter. However, it does not state return structure or conditions under which values differ from defaults, leaving some gaps.

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 extremely concise, with no filler. The front-loaded format immediately identifies the tool and its purpose. Every word earns its place.

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 the simplicity of a zero-parameter getter with no output schema, the description provides the key facts: what is fetched, where it comes from, and default format. It lacks explicit mention of the return type (array of INT16) but implies it. Nearly complete for a trivial tool.

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?

With 0 parameters and 100% schema description coverage, the description need not add parameter info. The baseline of 3 applies, and the description includes a note on the return format ('[INT16, default: 0,0,0,0]'), which is marginally helpful but not required for parameter 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?

Clearly states it retrieves raw accelerometer calibration offsets, contrasting with sibling tools like set_acc_calibration and calibrate_accelerometer. The verb 'Get' and resource 'acc_calibration' are specific and 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 phrase 'Do not edit manually' implies read-only usage, but no explicit guidance on when to use or alternatives is provided. With many sibling getters and setters, the description could more clearly indicate this is for reading calibration offsets and that calibration should be done via calibrate_accelerometer.

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