set_angle_feedforward

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

With no annotations, the description covers the basic behavior (setter, reduces lag) and parameter constraints (UINT8, 0–200, default 50). It does not disclose side effects, persistence, or required connection state, but is adequate for a simple parameter setter.

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?

Exceptionally concise: two sentences plus the range/default inline. No redundant words, all information is front-loaded and relevant.

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 low-complexity tool with one parameter and no output schema, the description is complete. It explains the purpose, effect, and valid values.

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% with min/max but no default. The description adds the default value (50) and the UINT8 type, providing clarity beyond the 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 'Set angle_feedforward' and explains its effect: 'Feedforward in angle mode — reduces lag when moving the angle setpoint.' This distinguishes it from the many other set_* tools and the get_angle_feedforward sibling.

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, no exclusions, and no context about prerequisites or scenarios where it should not be used.

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