set_small_angle

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

With no annotations, the description carries full burden. It explains the parameter's role as a pre-arm safety lock and explicitly includes range [UINT8, 0–180, default: 25], which provides behavioral bounds. It does not mention side effects or permissions, but the context is sufficient.

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 concise with no wasted words. It front-loads the purpose, then adds a key use case, and ends with the type/range/default. Every sentence earns its place.

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 one-parameter setter, the description covers purpose, range, default, and a critical use case. It does not discuss return values or error scenarios, but given the tool's simplicity, it is largely complete.

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 covers 100% of the single parameter. The description adds meaningful context beyond the schema: it explains that the parameter controls the arming tilt angle and specifies the default value (25), which aids understanding.

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 verb 'Set' and the resource 'small_angle', explaining it as a maximum tilt angle for arming—a pre-arm safety lock. This distinguishes it from sibling 'set_' tools by specifying its role in arming safety.

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 provides explicit guidance for using the value 180 with turtle/crash-flip mode, implying default usage for normal flight. It lacks explicit when-not-to-use or alternatives, but the use case is clearly stated.

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