set_blackbox_disable_alt

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 indicates a set operation that excludes altitude data. However, it does not disclose whether changes persist across reboots, require permissions, or have side effects on other blackbox settings.

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 very concise at 11 words, but it sacrifices clarity by not explaining the meaning of 'ON' vs 'OFF'. It could be more informative without becoming verbose.

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 boolean setting with no output schema, the description is minimally adequate. It lacks explanation of the effect when set to ON (presumably enables exclusion) and does not hint at any related parameters or prerequisites.

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 an enum of 'OFF' and 'ON'. The description adds 'default: OFF' but describes the parameter as 'UINT32' while the schema defines it as a string, creating a slight mismatch. No additional meaning beyond the schema is provided.

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 states the verb 'Set' and clearly identifies the resource 'blackbox_disable_alt' with the outcome 'Exclude altitude data.' It distinguishes from sibling tools like set_blackbox_disable_acc by specifying 'altitude data'.

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 when-to-use or when-not-to-use guidance is provided. The context is implied: use this to exclude altitude data from blackbox logs. No alternatives are mentioned, but the tool's purpose is straightforward.

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