hub

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

Annotations already flag destructiveHint=true / not readOnly, so the bar is lower, yet the description still adds real behavioral context: cutting port power cold-boots the board and un-enumerates its probe, the dashboard is a read-only live page on 127.0.0.1 whose URL is returned, and 'confirm' guards power/data cuts when a session is live. It stops short of stating permission/rate-limit or expected failure 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-loads the tool's identity, then compresses all seven action signatures into one dense line, then adds two short behavioral sentences. Nearly every clause carries information, though the signature list is terse enough to require careful reading.

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 7-action, 16-parameter mutation tool with no output schema, the description covers the action set, key defaults (channel mapping, state values), the dashboard return value, and the destructive cold-boot consequence. It omits returns for most non-dashboard actions and any sequencing guidance, so it is strong but not exhaustive.

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 coverage is 100%, so every parameter is already documented in the schema, and the inline action(...) signatures largely restate that mapping. The description does reinforce that channel is 1-based and defaults to the session's mapped channel, but adds little syntax or default information beyond what the schema already carries. Baseline 3 applies.

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?

Opens with a concrete verb+resource scoping ('Programmable USB hub: per-port power, USB2 data lines, cold boot, and V/I sampling') and then enumerates the seven actions with their signatures, so an agent immediately knows this is a hardware power/data control surface rather than a debug-inspection tool. It is clearly distinguishable from the surrounding debug/flash siblings.

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 action list implies the usage of each operation, and the note that 'Removing port power cold-boots that board and un-enumerates its probe' hints at when power cycling is appropriate. But there is no explicit when-to-use vs when-not-to-use guidance, no ordering advice among actions (e.g., discover before power), and no pointer to alternatives.

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