set_acc_trim_pitch

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

No annotations provided; description states it sets the value and includes range and default. However, it does not mention side effects, persistence, or disarm requirements, leaving behavioral 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?

Extremely concise: one sentence plus parenthetical range/default. Front-loaded with name and purpose. No redundant information.

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 single-parameter setter with no output schema, the description is adequate. It provides the necessary range and default, though it could mention relationship to calibration workflow.

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 already covers type and range (100% coverage). Description adds the default value (0) not present in schema, which is useful. No additional semantics beyond that.

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?

Description clearly identifies verb 'Set' and resource 'acc_trim_pitch', specifies it's for accelerometer pitch trim in level calibration. Distinguishes from sibling tools like set_acc_trim_roll and calibrate_accelerometer.

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 like set_acc_trim_roll or calibrate_accelerometer. Lacks context on prerequisites or whether it should be used before/after calibration.

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