set_blackbox_disable_bat

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 mutation ('Set') and mentions the data type and default, but fails to disclose whether the change persists across reboots, requires a reboot, or what side effects occur. The description is too brief to adequately inform the agent of behavioral traits.

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, consisting of one short sentence plus a type hint. It is front-loaded with the purpose and contains no redundant information. Every part earns its place.

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's simplicity (1 param, no output schema), the description covers the essential purpose. However, it lacks details on the exact effect of ON vs OFF, persistence, and any reboot requirement. For a complete picture, more context would be helpful.

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 full enum description. The description adds valuable context: 'Exclude battery data' explains the parameter's effect, and '[UINT32, default: OFF]' provides the data type and default value, which is not in the schema. This adds meaningful information beyond the structured 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 blackbox_disable_bat parameter to exclude battery data from blackbox logging. The verb 'Set' and resource 'blackbox_disable_bat' are unambiguous, and the purpose is easily distinguishable from sibling tools like get_blackbox_disable_bat or other set_blackbox_disable_* tools.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, consequences, or contrast with the get counterpart. For a parameter-setting tool, this is a significant gap.

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