get_runaway_takeoff_deactivate_delay

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

No annotations are provided, so the description bears the full burden. It discloses the value type, range, and default, but does not explicitly state that the tool is read-only or side-effect-free. The name implies a get operation, but a direct statement would improve transparency.

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 extremely concise: one sentence plus a bracketed spec. It is front-loaded with the purpose and includes essential details without wasted 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?

For a simple getter with no parameters and no output schema, the description covers meaning, type, range, and default. It is sufficient for the agent to understand and select 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?

There are no parameters (schema coverage 100%), so the description adds meaning by explaining the return value's semantics: a UINT16 from 100 to 1000 with a default of 500. This is useful context beyond the empty 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 it retrieves the 'runaway_takeoff_deactivate_delay' parameter, defines it as 'Time after arming before runaway takeoff protection stops monitoring,' and includes type, range, and default. The name and description distinguish it from siblings like 'get_runaway_takeoff_deactivate_throttle_percent'.

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: to read the current delay value. It does not explicitly say when not to use it or mention alternatives, but as a specific getter in a config toolset, the context is clear.

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