set_baro_i2c_address

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

No annotations provided, so description carries the burden. It states the parameter type (UINT8) and default (0), but does not disclose side effects like requiring a reboot or recalibration. Adequate for a configuration setter.

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?

Single concise line with inline annotations for requirement, type, and default. No wasted words; front-loaded with purpose.

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 parameter setter with one input, the description covers purpose, parameter meaning, requirement, and default. No output schema, but return values are implied. Complete enough for this complexity.

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 describes value as 'Value for baro_i2c_address (UINT8)'. Description adds 'I2C address override for barometer (0 = default auto-detect)' and default, providing meaning beyond schema. With 100% schema coverage, baseline is 3, but additional context raises it.

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?

Clearly states 'Set baro_i2c_address: I2C address override for barometer', distinguishing it from the sibling get_baro_i2c_address. The verb and resource are specific, and the description of 0 as auto-detect adds clarity.

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?

Specifies a prerequisite (Requires: USE_BARO) and explains the meaning of value 0 as auto-detect. While it doesn't explicitly contrast with alternatives like set_baro_i2c_device, the context is sufficient for a simple parameter setter.

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