refresh_customer_accounts

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

With no annotations, the description must disclose side effects, latency, or mutation behavior. It only says 'Trigger', failing to clarify if the refresh is synchronous or asynchronous, whether it modifies data permanently, or what the output schema represents.

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 a single, front-loaded sentence with no filler. It efficiently conveys the core action, though it could briefly mention the output or side effects without losing conciseness.

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?

Given the simple signature (one parameter) and absence of annotations, the description should at least hint at the output schema or behavior (e.g., returns a status or is fire-and-forget). It lacks sufficient detail for an agent to confidently invoke it correctly.

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 only parameter, 'customer_id', is required but the description does not add semantics beyond its name. With 0% schema description coverage, the agent must guess the format or constraints (e.g., UUID, length). No examples or additional context are provided.

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 action ('Trigger an aggregation refresh') and the resource ('all of a customer's accounts'). It distinguishes from sibling tools like get_customer_accounts (list) and delete_customer_account (delete), but does not elaborate on what 'aggregation refresh' entails, preventing a top score.

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?

No guidance is provided on when to use this tool versus alternatives, such as get_customer_accounts for viewing data or other refresh operations. No prerequisites or exclusions are mentioned, leaving the agent to infer usage context.

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