get_i_roll

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

Describes the effect of low and high values (drift vs slow wobble), providing insight into the behavior of the parameter. However, as a getter, it is inherently read-only, and the description does not explicitly state that.

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: two sentences plus a compact type/default note. Every sentence serves purpose: naming, functional explanation, consequence of wrong values, and technical specification.

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?

Despite no parameters or output schema, the description fully covers what the tool returns (roll I gain) and the implications of its value. An agent has enough information to decide to use this tool and interpret the result.

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 in the schema, so the baseline is 4. The description adds value by specifying the type (UINT8) and default (80), which helps the agent understand the expected value range even though no parameters are needed to retrieve it.

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 gets the Roll I gain, explains its function (corrects accumulated angle error, maintains attitude), and gives consequences of improper values. Distinguishes from sibling getters like get_p_roll or get_d_roll by naming the specific gain component.

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 explicit guidance on when to use this vs alternatives. The description implies it is for tuning the I-gain on roll axis, but doesn't mention when to adjust it relative to other PID gains.

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