get_baro_i2c_device

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

With no annotations provided, the description carries the full burden. It uses 'Get' implying a read-only operation, and provides the value range and default (UINT8, 0–5, default 0). This is sufficient transparency for a simple getter tool.

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: a single sentence plus a prerequisite note and type/range info. It is front-loaded with the purpose, and every part adds value without redundancy.

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 fully explains the return value (I2C bus number), its type (UINT8), range (0–5), and default (0). It also includes a prerequisite. This is complete for a simple configuration getter.

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 (schema is empty). Schema coverage is trivially 100%. The description does not need to explain parameters, and the baseline score of 4 is appropriate.

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 verb 'Get' and the resource 'baro_i2c_device' (I2C bus number for barometer). It distinguishes from sibling tools like get_baro_bustype, get_baro_hardware, and get_baro_i2c_address by explicitly mentioning 'I2C bus number'.

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 a prerequisite (USE_BARO) which provides context for usage. It does not explicitly state when not to use or provide alternatives, but given the specificity of the tool, the usage is clear and distinct from siblings.

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