Refresh Accounts

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

The description does not disclose that this is likely a network-triggering, potentially slow, and rate-limited operation. Annotations are all false, so no safety hints are conveyed beyond the description, which lacks behavioral details.

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 sentence that efficiently conveys the tool's purpose without extraneous words. It is front-loaded and easy to scan.

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 tool with no parameters and an output schema, the description is minimally adequate. However, it lacks context about side effects, expected duration, or when results are available, which is needed given the imperative nature of 'refresh'.

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?

With 0 parameters and 100% schema coverage, the schema fully documents the absence of parameters. The description adds no parameter information, meeting the baseline of 3 for high schema coverage.

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 verb 'refresh' and the resource 'account data from financial institutions', indicating it triggers a data sync. It distinguishes from sibling tools like 'get_accounts' which likely retrieve cached data without initiating a refresh.

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 like 'get_accounts' or 'create_manual_account'. The description does not mention prerequisites, timing, or whether it should be called sparingly.

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