open_hw_manager

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 the key behavioral boundary — that opening the manager does not establish a JTAG connection — which is genuinely useful. However, it says nothing about whether an active session is required, what happens if the manager is already open, or how to close it (the sibling close_hw_manager is never referenced).

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?

A single short sentence with the essential scoping nuance front-loaded. Nothing is wasted and nothing extraneous is bolted on.

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 zero-parameter, no-output-schema state-setup tool, the definition is nearly complete. The only missing context an agent would want is the session prerequisite and the natural follow-up (connect_hw_server / close_hw_manager).

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless invocation.

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?

Specific verb+resource: 'Open the Hardware Manager'. The parenthetical '(no JTAG connection yet)' distinguishes it from connect_hw_server and close_hw_manager, making the scope of the operation clear 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?

Usage is only implied: the 'no JTAG connection yet' clause hints that connect_hw_server should follow, but there is no explicit when-to-use statement, no prerequisites (e.g. an active session), and no named alternative.

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