Sync with ZenMoney

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

Annotations already declare readOnly, idempotent, and closed-world. The description adds the crucial non-obvious fact that sync is automatic, so a caller knows this is a manual override – behavior not captured by any annotation.

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 clauses: one naming the action and the auto-sync caveat, one defining the boolean. Every sentence earns its place and the primary purpose is front-loaded.

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 single optional boolean with no output schema, the description gives what's needed: what it does, that it's normally automatic, and what full does. Only minor gap is that it doesn't say what 'pull' returns or whether concurrent calls are safe, but annotations cover safety.

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 coverage is 0% and the only param is 'full' with no description. The description supplies the semantics: full=true re-downloads everything, versus an incremental pull by default. This directly compensates for the undocumented param.

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 (pull) and resource (changes from ZenMoney), with a clear action. Doesn't explicitly compare to siblings, but the 'auto-sync' note distinguishes it from the read tools in the list.

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 parenthetical explains that syncing already happens automatically after TTL expiry, which tells the agent when this tool is actually needed (to force a refresh). No explicit exclusions, but the context is clear.

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