bowire.invoke

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

No annotations are provided, so the description carries the full behavioral burden, and it does not discharge it. It says nothing about whether the invoked method mutates state (destructive vs read-only depends entirely on the remote method), authentication requirements, error behavior, or rate limits — significant gaps for a tool that can trigger arbitrary RPCs.

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 tight sentences with no waste; the purpose is front-loaded and the format clarifications follow. Every clause earns its place.

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?

The 100%-covered schema compensates for most parameter detail, and no output schema exists so return values need not be explained. But with six parameters, no annotations, and an arbitrary-RPC capability, the description is thin on behavior and error/permission context an agent would want before invoking.

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 schema already documents all six parameters, giving a baseline of 3. The description's notes ("body is a JSON string", "metadata is a flat object of header / gRPC metadata") largely restate the schema's own descriptions rather than adding new semantics.

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?

States a specific verb (invoke) plus resource (a unary method) and explicitly ties it to its upstream sibling bowire.discover. An agent can distinguish this from tools like bowire.subscribe or bowire.assert without opening a 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?

"discovered via bowire.discover" establishes the prerequisite that the method must first be discovered, which is genuine usage context. However, there is no when-not guidance and no mention of alternatives or exclusions, so usage is only implied rather than spelled out.

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