get_horizon_delay_ms

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

No annotations provided, but the description explains the behavioral effect: 'Delays return-to-level for a more acro-like feel.' This adds context beyond just reading a value. No side effects or permissions mentioned, but not critical for a read operation.

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 note. No redundant information. Every part adds value.

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 is complete. It explains the purpose, the parameter's effect, and the expected value type and range.

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?

Input schema is empty (no parameters), so schema coverage is 100%. The description adds value by specifying the expected return type and range: '[UINT16, 10–5000, default: 500]', which helps the agent interpret the result.

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 gets 'horizon_delay_ms' and explains what it is: 'Time (ms) before horizon mode re-applies leveling after sticks return to center.' It also distinguishes from siblings by specifying the exact parameter name and effect.

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?

No explicit guidance on when to use this tool versus alternatives. However, as a simple getter with no parameters, the need for guidelines is minimal. The agent can infer usage from the name and description.

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