get_failsafe_recovery_delay

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

No annotations are provided, so the description carries the full burden. It discloses the data type (UINT16), range (1-200), default value (5, equivalent to 0.5 s), and the parameter's behavioral context (duration for signal stability). While it doesn't explicitly state that this is a read-only operation, the nature of a 'get' tool implies it, and the details given are 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 a single sentence that efficiently conveys the tool's purpose, the parameter's meaning, and its constraints. Every part is informative with no redundancy or unnecessary words.

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 zero input parameters and no output schema, the description fully explains the return value and its context. It covers the parameter's purpose, range, default, and unit, making it complete for an agent to understand and use the tool correctly.

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 no parameters (100% coverage by default). The description adds meaning beyond the schema by explaining the output parameter's semantics, valid range, default value, and unit. This is above the baseline of 3 for high schema coverage.

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 failsafe_recovery_delay parameter. It explains what the parameter represents (duration the signal must be stable after Stage 2) and distinguishes its role in two contexts (re-arming and GPS Rescue stick input assessment). This specificity differentiates it from other getter 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 when needing to know the recovery delay for failsafe recovery. However, it does not explicitly state when to use this tool versus other failsafe-related getters (e.g., get_failsafe_delay) or when not to use it. No alternatives or exclusions are mentioned.

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