broker_call_tool

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

No annotations provided, so description must fully disclose behavior. It mentions mutating-tool policy gated by profile allowlist and serialization when configured, but lacks discussion of side effects, error handling, or return format.

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 dense sentences, no redundancy. Purpose is front-loaded, each sentence adds essential guidance.

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?

No output schema; description does not mention return value (only schema description says 'returns upstream result'). Missing info on what to expect after invocation, though prerequisites are well covered.

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?

100% schema coverage, but description adds meaningful context: arguments must be exact upstream schema, empty object only if upstream accepts none. Name must be broker-qualified from prior describe/search.

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?

Description clearly states 'Call one profile-visible upstream MCP tool through the broker', specifying verb and resource. It distinguishes from siblings like broker_describe_tool and broker_search_tools by focusing on invocation.

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?

Explicit guidance to call broker_describe_tool first and pass only accepted arguments. Instructs to use broker-qualified names from prior tool results, not unqualified upstream names.

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