set_pitch_srate

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 adds the default value (67) and type (UINT8), which informs the valid input range beyond the schema's lax constraints. However, it does not disclose whether the setting is live or requires a reboot, or any other behavioral implications.

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 very concise—a single line with a colon and brackets. It efficiently conveys the action, parameter type, and default. It could benefit from slightly more structure but remains appropriate for a simple setter.

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?

Given the tool's simplicity (one parameter, no output), the description is mostly complete with the default and type information. However, it omits an explanation of what 'pitch super rate' means and does not mention the valid range enforcement, which is important given the schema's wide bounds.

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?

The schema already describes the parameter 'value' as 'Value for pitch_srate (UINT8),' achieving 100% coverage. The description adds the default value '67,' which the schema lacks, providing additional semantic value beyond the structured definition.

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 'Set pitch_srate: Pitch super rate,' which identifies the action and the specific parameter being set. The tool name and description together make the purpose evident, distinguishing it from sibling tools like set_roll_srate. However, no elaboration on what 'pitch super rate' means is provided.

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, such as checking get_pitch_srate first or understanding the effect on flight modes. There is no mention of prerequisites, side effects, or exclusions.

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