sync_now

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

With no annotations provided, the description discloses that it is a network call, it respects a request budget, and it returns a summary with errors. It implies a cache-update operation. It could add details about side effects or permissions, but it is transparent about key behaviors.

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 two sentences long, with the first sentence stating the core purpose and the second providing essential behavioral constraints. No superfluous words; front-loaded and efficient.

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 existence of an output schema (not shown), the description doesn't need to detail return values. It covers the tool's function, budget constraints, parameter behavior, and error handling. Minor gaps: no mention of cache duration or authentication requirements, but overall sufficient for a simple tool.

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 schema description coverage is 0%, so the description must add meaning. It explains how the 'days' parameter influences the number of requests: 'a sync of >89 days makes one request per ~89-day window.' This adds behavioral context beyond the schema's basic type and default.

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: 'Pull fresh data from SimpleFIN into the cache (network call).' It identifies the data source, the action (pull), and the target (cache). While it doesn't explicitly differentiate from siblings, the verb 'sync' and context imply a distinct refresh operation.

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?

The description explains when to use the tool (to sync data) and provides critical context about respecting SimpleFIN's daily request budget and how the 'days' parameter affects request count. However, it does not mention alternatives or when not to use the tool.

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