refresh_accounts

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

Without annotations, the burden is on the description to disclose behavioral traits. 'Refresh the list' implies fetching updated data, but it doesn't clarify side effects (e.g., overwriting local state), idempotency, or required authentication. This is insufficient for a mutation-like tool.

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 extremely concise—one sentence with 7 words—providing the essential verb and resource without extraneous information. Every word earns its place.

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 simplicity (one optional parameter, no output schema) and the presence of sibling tools, the description is incomplete. It lacks details on what 'refresh' means behaviorally, when to use it, and how it differs from similar tools like 'search_accounts' or 'get_account_health'.

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 input schema has 100% coverage for the single parameter 'limit', which includes a clear description and default. The tool description adds no additional meaning beyond the schema, earning the baseline score.

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 'list of accounts', providing a specific purpose. However, it doesn't differentiate from sibling tools like 'search_accounts' or 'find_account_by_name', which may have overlapping functionality.

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 whether it should be called periodically or after certain actions. The description lacks exclusions or context for appropriate usage.

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