set_d_pitch

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 that the actual D is boosted toward d_max_pitch on fast moves, revealing behavioral dynamics beyond a simple parameter set.

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 four concise sentences, front-loaded with purpose, and includes a data type hint. No unnecessary 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 single-parameter set tool, the description provides essential behavioral context and references related parameter (d_max_pitch). It lacks prerequisites or side effects but is largely complete for a simple PID adjustment.

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%, but the description adds rich context: the value is a UINT8 with default 34, and explains its effect during smooth and fast flight, which is far beyond the schema's minimal description.

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 sets the base D gain for pitch, active in smooth flight and boosted during fast moves. It distinguishes itself from siblings like get_d_pitch and set_d_max_pitch by specifying the axis and the boosting behavior.

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?

The description implies when to use (for setting base D pitch) but does not explicitly state when not to use or provide alternatives. Usage is inferred from purpose, lacking explicit guidance.

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