set_angle_limit

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

With no annotations, description discloses the parameter's effect (maximum tilt angle during flight) and constraints (UINT8, 10-80, default 60). Does not mention side effects, persistence, or prerequisites like disarm state. Adequate but not thorough.

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?

Single sentence plus bracketed information. Directly states purpose and constraints with no wasted words.

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?

Sufficient for a simple parameter setter among many siblings. Lacks information about when changes take effect (immediate? reboot?) and any prerequisites (disarmed state). No output schema but not critical.

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% (type, range, required). Description adds context: 'degrees', 'angle mode', 'flight-time', and default value. Provides meaning beyond bare 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?

Description clearly states the tool sets 'angle_limit' (maximum tilt angle in angle mode during flight) with unit, data type, range, and default. This distinguishes it from other set_* tools.

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 other angle-related settings (e.g., set_angle_p_gain, set_angle_feedforward). Context of 'angle mode' is implied but not contrasted with alternatives.

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