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 discloses only that history is returned; it says nothing about what the bridge does with the instruction, whether the call mutates remote state, what permissions are needed, or how long history is retained.

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 tight sentence with no filler, and the action is front-loaded. It earns its place, though it is arguably too terse for the ambiguity of the tool.

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?

With no annotations, no output schema, and 0% parameter coverage, the description should compensate but does not. An agent cannot tell what the bridge is, what happens to the instruction, or what 'history' contains.

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 single 'instruction' parameter is undocumented in the schema. The description only repeats the parameter's name implicitly ('send instruction') without format, length, or content expectations, adding almost no meaning.

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 gives a verb ('Send instruction') and names a mechanism ('OpenClaw bridge') plus a return value ('history'), so the basic action is inferable. However, 'forward' is generic and the description does not distinguish it from the sibling 'converse', which plausibly also sends instructions to the same bridge.

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?

There is no statement of when to use this tool versus alternatives like 'converse' or 'telegram-pairing-approval'. The agent must guess at the routing decision from the name alone.

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