set_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 explains the behavioral effect on re-arming and stick input assessment, but does not disclose side effects, persistence, or required permissions. Slightly better than minimal.

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?

Two concise sentences, front-loaded with the purpose. No filler 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 the tool is a simple parameter setter with no output schema, the description covers the parameter's role in failsafe stages, re-arming, and GPS Rescue. It includes range and default. Minor gap: no mention of when changes take effect.

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 a description, but the tool description adds meaning by explaining the parameter's effect in the failsafe flow and provides the default value (5 = 0.5s), which is not in 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?

The description clearly states the tool sets the failsafe_recovery_delay parameter and explains its meaning in the context of failsafe Stage 2, re-arming, and GPS Rescue. It distinguishes from other failsafe-related tools like set_failsafe_delay.

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 provides clear context about when the parameter applies (after Stage 2) but does not explicitly state when to use this tool versus alternatives. No exclusionary guidance is given.

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