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

With no annotations, the description carries the full burden; 'Queue' usefully signals asynchronous, non-blocking behavior rather than a synchronous fetch. However, it omits whether repeated calls are safe, whether it is rate-limited (notable given the get_rate_limit_status sibling), and whether it requires authorization.

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, front-loaded sentences with the action stated first. The trailing 'Args: connection_id.' duplicates the schema and is the one low-value fragment.

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 one-parameter trigger tool with no annotations and no output schema, the description covers the core action reasonably. It still leaves open what the queue actually returns, whether side effects are incurred, and how to obtain a valid connection_id.

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 0% for the single parameter, so the description must compensate and it only does so minimally by naming the argument. It does not explain the ID format or that connection_id comes from list_connections, leaving the agent to infer the source.

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 ('Queue ... refresh') and the resource scope ('for one connection'), and the 'balance/usage/plan' detail clarifies what is refreshed. It does not explicitly contrast with siblings like list_connections or get_rate_limit_status, but the action is unambiguous.

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?

'Immediate' hints that this is an on-demand alternative to scheduled refreshes, but the description never states when an agent should call this versus list_connections or get_overview, nor any prerequisites. Usage must be inferred from the name alone.

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