broker_call_tool

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

Discloses the broker's mutating-tool policy is gated by the profile's allowlist, and hints at server-side projection to cut tokens and latency. Missing details on error handling or response format, but acceptable given no annotations.

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 sentences with no wasted words. The first sentence states purpose, the second provides a critical usage guideline. Highly efficient.

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?

Covers invocation, policy, and prerequisite steps. Lacks explicit statement about return format (dynamic), but the projection parameter description partially compensates. Enough for a proxy tool with variable output.

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 coverage is 100%, so baseline is 3. The description adds context that names must come from broker_search_tools or broker_describe_tool, but does not significantly enhance understanding beyond the schema descriptions.

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 the tool invokes an upstream MCP tool via the broker using a qualified name and arguments. It distinguishes from sibling tools (broker_describe_tool, broker_search_tools, broker_status) by focusing on execution.

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?

Explicitly advises calling broker_describe_tool first and passing only accepted arguments, providing clear when-to-use guidance and key steps for correct invocation.

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