sync_now

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

No annotations, so the description carries the full burden. It usefully discloses that this bulk refresh is normally a daily background job (implying it is heavy / a fallback), but says nothing about cost, duration, rate limits, or how it interacts with the cache (overwrite vs merge). For an unannotated bulk mutation of local state, that leaves gaps.

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 tight sentences with the action front-loaded and the trigger condition immediately after. No filler.

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 2-param, no-output-schema, no-annotation tool, the description explains the operation and its default trigger but omits all parameter meaning and any sense of return/status (e.g., relationship to cache_status). Adequate but with clear gaps.

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%, so the description must explain the two parameters and does not. Neither provider_id nor history_days is mentioned; in fact 'pull everything' sits uneasily with a provider_id that would narrow the scope, leaving an ambiguity the agent cannot resolve.

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 concrete verb and effect: 'Pull everything from the bank into the local cache.' The phrase 'rather than one account' implicitly scopes it against the per-account readers in the sibling list, giving reasonable differentiation, though it never names a specific sibling tool.

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?

Gives explicit when-to-use guidance ('call it when you need the whole cache refreshed rather than one account') and notes the normal trigger is a daily scheduled job, so the agent knows this is the manual override. It stops short of naming which sibling to prefer for single-account reads.

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