bw_write_open_hub

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

With no annotations supplied, the description carries the full behavioral burden, and it does not state that this is a mutating, activating write that alters repository objects. Nothing is said about required authorizations, transport recording, whether an existing destination is overwritten, or what happens on partial failure. Nearly all behavioral detail is deferred to bw_describe, leaving the agent dependent on a second call before understanding the operation's side effects.

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 short sentences, front-loaded with the purpose, with the pointer to the enum and bw_describe placed second where it belongs. Nothing is padded, but the deferral pattern means the text is lean partly by shifting detail rather than by efficiently summarizing it.

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 29-parameter tool with nested objects, no annotations, and no output schema, the progressive-disclosure design (enum plus bw_describe pointer) is coherent, but the description alone leaves the agent without mutation semantics or authorizations. It is adequate as an entry point, not as a self-contained definition.

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 100%, so the baseline is 3 and the schema already tags each parameter with its applicable operation and notes like "existing fields are kept" and "an empty array clears the key." The description itself adds no parameter meaning; it only points at the enum and bw_describe, so it neither improves nor undermines the schema.

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 specific verb pair and resource: "Create or change an Open Hub Destination." The resource is distinctive enough that an agent can separate it from bw_write_adso, bw_write_dtp, and the other bw_write_* siblings without opening a schema, though it never explicitly contrasts itself with them.

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?

It gives indirect routing advice — check the operation enum for requirements, call bw_describe for a full per-operation parameter definition — which is genuinely useful procedural guidance. It says nothing about when a caller should choose this tool over activating, deleting, or reading an existing destination, and there is no create-vs-update selection advice beyond the schema enum.

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