get_blackbox_high_resolution

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

No annotations exist, so the description carries the full burden. It discloses the behavioral effect (doubles precision for specific fields) and side effect (increases log size). It also mentions data type (UINT8) and default (OFF). This is good transparency for a read operation. No contradictions.

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 a single sentence with a parenthetical note. It is concise, front-loaded with the action, and every part adds value. No 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?

The tool has no parameters and no output schema. The description explains the effect and side effect, but does not specify the return format (e.g., whether it returns ON/OFF, 0/1, or the actual value). For a simple getter, this is a notable gap. Otherwise complete.

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?

The input schema has no parameters (0 params, 100% coverage). The description does not need to explain parameters. It adds context about what the tool retrieves (the high resolution setting). Baseline for 0 params is 4.

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 action ('Get') and the resource ('blackbox_high_resolution'). It explains the effect: doubling data precision for gyro and setpoint fields. It also mentions a side effect (increases log size) and provides data type and default. This distinguishes it from sibling getters that retrieve other settings.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only implies a trade-off by noting that it increases log size, but does not explain scenarios where this would be beneficial or detrimental. No comparison with other getter tools or when to prefer this setting.

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