configure_bus_iic

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 does disclose a default (addr_bits default 7), the meaning of exchange (swaps channel sources), and that display enables the decoding bus — useful behavioral detail. However it is silent on persistence across power cycles, whether reconfiguring an already-configured bus resets other settings, and any error behavior.

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?

Front-loaded purpose line, then one compact line per parameter with no filler or restatement of the tool name. Every sentence 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?

An output schema exists, so return values need not be explained, and the parameter set is well covered. What remains thin is the surrounding workflow context — prerequisites, interaction with configure_bus_get_bus_config, and state side effects — which a mutation tool with no annotations could reasonably supply.

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 description coverage is 0%, so this description is doing the work: it supplies allowed value families (CH1..CH4 or D0..D15), the addr_bits value set 7|8|10 with default 7, and the semantics of exchange and display. Only the required 'bus' parameter (self-evident from the name) is left undocumented, hence not a perfect 5.

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?

States a specific verb+resource ('Set Bus <n> to I2C decoding and configure it') and the protocol name distinguishes it cleanly from the many siblings (configure_bus_spi, configure_bus_can, configure_bus_iis, etc.). An agent can select this without opening any schema.

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 implies the setup role (decode configuration must precede read_bus_data) but never states when to use this versus configure_bus / configure_bus_parallel / read_bus_data, nor any prerequisite such as enabling the bus first. Usage is inferable but not explicit.

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