get_blackbox_disable_servos

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

With no annotations, the description carries the burden. It explains that the tool gets a setting that excludes servo data from logs, and notes it is a UINT32 with default OFF. This goes beyond the name but could mention that it is read-only and non-destructive.

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 with a prerequisite note and a type/default note. Every element is necessary and front-loaded with the action.

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 no output schema, the description sufficiently explains what the tool returns (the state of servo exclusion). It could elaborate on the exact meaning of the UINT32 value, but for a simple getter 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?

There are no parameters, so the description adds value by describing the setting itself (UINT32, default OFF). Since schema coverage is 100% (no params), baseline is 4, and the description meets that.

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 that the tool retrieves the setting to exclude servo output data from logs. The verb 'get' matches the resource 'blackbox_disable_servos', and it is distinct from siblings like 'get_blackbox_disable_acc' by specifying 'servo output 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?

The description mentions the prerequisite 'Requires: USE_SERVOS', which guides when the tool is applicable. However, it does not explicitly state when to use this tool versus alternatives like 'set_blackbox_disable_servos' or other 'get_blackbox_disable_*' tools, but 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.