get_raw_imu

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

No annotations provided; description only states what data is returned. No disclosure of frequency, real-time nature, side effects, or blocking behavior. Bare minimum for a read operation.

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?

Single 13-word sentence front-loads the purpose and lists data types with units. No wasted words or redundancy.

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?

Adequate for a simple parameterless tool, but lacks details on output format (e.g., single snapshot vs. stream) and whether all three sensors are returned together. No output schema to compensate.

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?

No parameters in schema (0 params, 100% coverage). Baseline of 4 applies as description does not need to explain parameters. It correctly omits parameter info.

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 verb 'Get' and resource 'raw IMU sensor data' with specific measurement types (accelerometer, gyroscope, magnetometer) and units (G, °/s). Distinguishes from sibling tools like 'get_attitude' or 'get_acc_calibration'.

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. Does not mention scenarios (e.g., debugging, calibration) or prerequisites. Sibling tools like calibrate accelerometer/magnetometer exist but no comparison provided.

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