open-delegate bridge diagnostics

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

The description declares it is 'read-only' and lists what information is returned, but does not detail performance characteristics or rate limits. Since no annotations are provided, this is adequate.

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?

Two dense sentences front-load all critical information (purpose, scope, contents) and then provide usage guidance. No wasted words.

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 explains the return contents well (pid, version, logs, etc.). It lacks specifics on format, but covers the breadth sufficiently.

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 zero parameters, so baseline is 4. The description adds no param information, which 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 it is a read-only snapshot of the bridge itself, listing specific outputs (pid, version, log paths, runtimes, events, session counts). It distinguishes itself from sibling tools that operate on sessions.

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 explicitly states when to use: to diagnose host-side connection errors or to find which process/log backs a runtimeKey. It implies not for session-specific diagnostics.

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