set_gps_rescue_yaw_p

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 the value range (UINT8, 0–200) and default (20), implying it updates the parameter. However, it does not explain persistence, side effects, or whether a reboot is required. This is acceptable for a simple parameter setter but could be improved.

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 (one sentence plus bracket info) and front-loaded with the purpose. Every word is necessary, and there is no fluff.

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 set tool with one parameter and no output schema, the description adequately covers intent, parameter range, and default. It could mention persistence or related parameters, but it is sufficient for the tool's 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?

Schema coverage is 100%, so baseline is 3. The description adds semantic value by explaining the parameter's role ('Yaw P gain during rescue (heading correction)') and providing range/default info. This goes beyond the schema's generic description ('Value for gps_rescue_yaw_p').

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?

The description clearly states the tool's function: 'Set gps_rescue_yaw_p: Yaw P gain during rescue (heading correction)'. It uses a specific verb (Set) and resource (gps_rescue_yaw_p), and provides context (Yaw P gain during rescue) that distinguishes it from sibling tools like 'get_gps_rescue_yaw_p' and other set_* parameters.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or related tools (e.g., other GPS rescue PID gains). The agent must infer usage from the name alone.

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