Refresh broker data

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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool bypasses caching, refreshes all configured brokers, and returns per-broker success/failure. It stops short of mentioning rate limits, failure details, or whether the operation is safe/idempotent, but the core behavior and return shape are clear.

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?

The description is two tight sentences with no filler. The most important behavioral fact, cache bypass, is front-loaded, and the return value is stated succinctly.

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 zero-parameter refresh tool, the description is largely complete: it explains the action, the reason (bypass cache), the scope (every configured broker), and the result format. It lacks minor context such as potential slowness or error handling, but nothing essential is missing for correct invocation.

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?

The tool has zero parameters and the schema is empty, so there are no parameter semantics to document. The baseline of 4 applies because the description fully covers what an agent needs to know about invocation: no arguments are required.

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 states a specific action ('Bypass the 5-minute cache and re-fetch every configured broker right now') with a clear resource and behavior. It also distinguishes itself from sibling query tools like broker_accounts and broker_stats by focusing on refreshing rather than reading data.

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?

The description clearly implies when to use this tool: when cached broker data is stale or up-to-the-minute data is needed. It does not explicitly name alternatives or exclusions, but the cache-bypass framing provides enough context to select it over read-only sibling tools.

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