get_imu_dcm_kp

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

No annotations provided; description implies a safe read operation but does not explicitly state that the tool is non-destructive or has no side effects. Adequate but could be more precise.

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?

Three sentences: defines the parameter, explains its effect, notes default suitability, and provides constraints. No redundancy, efficiently front-loaded.

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?

Complete for a parameterless getter; covers purpose, typical use, and value constraints. Could mention return format (single uint16) but not essential given simplicity.

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 exist, so schema coverage is 100%; description adds relevant type, range, and default value, which compensates for the absence of an output schema.

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 the tool retrieves the complementary filter proportional gain, explains its role in blending accelerometer data with gyro integration, and distinguishes it from sibling tools like get_imu_dcm_ki.

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?

Notes that the default is suitable for normal use, implying a read operation; does not explicitly mention when to adjust via the setter, but context is clear for a simple getter.

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