get_crash_limit_yaw

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

No annotations provided, so the description carries full burden. It includes the parameter's data type, range, units, and default, which informs the agent about the expected return value. However, it does not disclose potential side effects (none expected) or specific conditions like needing a connection to the flight controller.

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 a single sentence that includes all necessary information without redundancy. It is efficiently front-loaded with the parameter name and purpose, followed by concise technical details in brackets.

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 zero-parameter input and no output schema, the description provides sufficient contextual completeness. It fully explains what the tool does and the nature of the returned value. The agent can confidently use this tool to read the crash limit yaw parameter.

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 input schema has zero parameters, so schema coverage is trivially 100%. The description adds semantic meaning beyond the schema by specifying units (deg/s), allowed range (0–1000), and default value (200), which helps the agent interpret the returned value correctly.

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 tool retrieves the 'crash_limit_yaw' parameter, specifying its purpose (yaw rate limit during crash recovery), units (deg/s), data type (UINT16), range (0–1000), and default value (200 per profile). It distinguishes from sibling tools like 'set_crash_limit_yaw' and other get_crash* 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?

The description implies usage context by naming the parameter and its role in crash recovery. While it does not explicitly state when to use or alternatives, the purpose is straightforward for a getter, and the sibling setter is implicitly the alternative for writing. Lacks explicit when-not-to-use guidance.

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