set_crashflip_rate

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

With no annotations provided, the description carries the full burden and does disclose the parameter's effect (sets a rate limit), but does not mention whether the setting persists or requires a save/reboot, or any side effects. The disclosure of the range and default is helpful but incomplete for full behavioral transparency.

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 extremely concise: a single sentence with the key information (action, resource, units, special value, range, default) presented clearly. No unnecessary words or redundancy.

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 schema, no nested objects), the description covers the essential aspects: purpose, parameter meaning, range, units, special value, and default. Missing a mention of persistence or side effects, but for a simple setter this is nearly 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 description adds semantic value beyond the input schema by explicitly stating that '0 = unlimited' and providing the default value. The schema already covers the range and description, so the added context about the special meaning of 0 and the default enhances 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 that the tool sets the rotation rate limit during crash flip mode, specifying units (degrees/s) and the special value 0 meaning unlimited. The verb 'Set' and resource 'crashflip_rate' are precise, and it distinguishes from the many sibling set_* tools by focusing on this specific parameter.

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 usage when configuring crash flip behavior, but lacks explicit guidance on when to use this tool versus alternatives like get_crashflip_rate or related set_crashflip_* tools. It would benefit from a note that this is for setting the rate limit specifically.

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