get_failsafe_landing_time

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

The description explicitly states this tool reads the failsafe landing time value and provides the data type, range, and default. It implies a read-only operation without side effects. No annotations are present, so the description carries the full burden, which it meets adequately by confirming the behavior.

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 followed by a brief technical note. It is front-loaded and concise, with no redundant information. It could be slightly improved by separating the technical details for clarity, but it is effective.

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 simple nature of the tool (no output schema) and the presence of sibling tools, the description provides sufficient context: the parameter's type, range, and default. It could be more complete by explaining that the value is in units of 0.1 seconds (as inferred from '60 (6 s)'), but overall it is adequate.

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 tool has zero parameters, and the input schema is empty (100% coverage). The description adds value beyond the schema by describing the returned value: UINT8 with range 0–250 and default 60 (6 seconds). This provides meaningful context about the output.

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 it retrieves 'failsafe_landing_time', which is the duration of Landing Mode Stage 2. The verb 'Get' and the specific resource make the purpose unambiguous, and it is distinct from the sibling 'set_failsafe_landing_time' tool.

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 for reading the current failsafe landing time setting, but provides no explicit guidance on when to use this tool versus alternatives like 'get_failsafe_delay' or 'set_failsafe_landing_time'. No exclusion or conditional usage is mentioned.

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