get_crashflip_rate

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

No annotations are present, so the description carries the full burden. It correctly implies a read operation but does not explicitly state that calling it is safe and has no side effects. The description adds some context (range, units) but lacks explicit behavioral disclosure.

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, consisting of one sentence plus an inline specification. It front-loads the tool name. However, it repeats the tool name unnecessarily, and the inline spec could be integrated more naturally. Overall efficient.

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 no output schema, the description does not explicitly state what is returned (presumably the current value). It provides range and default but could be more complete by indicating that the tool returns the current setting. For a simple getter, it is adequate but not fully comprehensive.

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?

There are no parameters, so schema coverage is trivially 100%. The description adds meaningful context by explaining the meaning of the parameter value (rotation rate limit), units, range, and default. Since there are zero parameters, baseline is 4.

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 what the tool does: it retrieves the crashflip_rate parameter, which is a rotation rate limit during crash flip mode. It specifies units (degrees/s), valid range (0-250), and default value (0). This is specific and distinguishes it from other getters.

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 is provided on when to use this tool versus alternatives, such as the related set_crashflip_rate tool. The description does not mention any prerequisites or typical usage context (e.g., getting before setting).

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