configure_bus_parallel

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

With no annotations, the description carries the full behavioral burden. It does disclose useful traits: manual-derived defaults (endian NEGative default), the analog-source width restriction (1..4), and that display 'enable[s] the decoding bus' (a visible side effect). However, it never says whether configuring overwrites an existing bus setup, whether other bus settings are reset, or what the response looks like.

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?

Purpose is front-loaded in one line, followed by a scannable parameter list where each line earns its place. Slightly dense and the indented continuation lines ('(USER enables the per-bit sources below)') are a little awkward, but there is no filler.

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 described. For a 10-parameter, zero-coverage config tool the description is strong on parameters and adequate on behavior; the only real gap is the absence of any statement about how this configuration interacts with pre-existing bus settings.

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% and the schema has no enums, so the description must carry all semantics — and it does. It documents every one of the 10 parameters with concrete allowed values (bus_source D7D0|D15D8|...|USER, clk CH1..CH4|D0..D15|OFF, clk_slope POS|NEG|BOTH, width 1..16, bit range 0..width-1, endian, polarity, display) and flags the cross-parameter dependency between bit_source and BUS_source.

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 opening sentence states a specific verb and resource: 'Set Bus <n> to PARallel decoding and configure it,' with a manual section reference. Against a sibling set full of configure_bus_rs232/iic/spi/can/lin/etc., the word PARallel uniquely identifies which bus protocol this tool configures.

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?

Usage is implied by the protocol name but never stated: there is no 'use this when decoding a parallel bus' and no comparison to the other configure_bus_* siblings. The per-parameter notes ('USER enables the per-bit sources below', 'BUS_source must be USER') give conditional guidance, but only at the parameter level, not tool selection.

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