accounts.reload

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the important behavior that server cache state is mutated from the on-disk source, but says nothing about whether the reload replaces or merges existing entries, whether it is idempotent, whether it fails on malformed files, or what permissions are required.

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?

A single short sentence with the action front-loaded and the side effect parenthetical at the end. No filler, nothing to trim.

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 simple parameterless reload, the core operation is conveyed, but with no output schema and no annotations the description omits what the call returns (e.g. count of loaded accounts) and how errors surface. These gaps are minor but real for an agent deciding whether to call it.

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 takes zero parameters (empty object schema), so there is nothing for the description to disambiguate. Baseline for a parameterless tool applies.

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 (reload) and resource (accounts registry) plus the mechanism (from disk) and side effect (updates server cache). This clearly separates it from siblings accounts.list, accounts.upsert and accounts.delete, though it never names an alternative outright.

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?

Usage is only implied: reloading 'from disk' suggests the caller should invoke it after the on-disk registry has changed. There is no explicit when-to-use, when-not-to-use, or comparison to accounts.upsert/accounts.list for refreshing state.

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