bridge_context

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: it mentions update but not which inputs cause a write, whether writes overwrite existing state, whether they are reversible, or what permissions are needed. The read/update split is the one useful hint, but it is not operationalized.

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?

It is a single front-loaded sentence with no filler, which is structurally fine. But the brevity comes at the cost of specification — the sentence is too compressed for a multi-mode tool with three undocumented parameters.

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?

A dual read/write tool with no annotations, no output schema, and 0% parameter documentation needs far more than one sentence. Nothing explains the mode-selection logic, the return shape, or how this differs from bridge_context_pull, so an agent cannot confidently invoke it.

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 none of the three parameters (topic, write_body, write_topic) are explained in the description. Only the write_ prefix and the word "update" weakly imply a read-mode topic versus write-mode body/topic, leaving the caller to infer the contract entirely from parameter names.

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 names a verb pair ("read or update") and enumerates four resource areas (status, branch binding, claims, scratchpad), so the domain is identifiable. However, it does not distinguish this tool from the sibling bridge_context_pull, and the "read or update" duality leaves the actual operation ambiguous rather than specific.

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 guidance on when to choose this tool over bridge_context_pull or the other bridge_* siblings, and no indication of prerequisites or preconditions. An agent has to guess whether this is the general entry point or a write-specific variant.

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