sync_zenmoney

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

No annotations are provided, so the description bears the full burden. It mentions the /v8/diff/ endpoint and the ability to force a full re-download, but does not disclose side effects, whether synchronization mutates local or remote state, authentication requirements, or what the operation returns. These gaps are significant for a sync operation with no annotation support.

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 concise sentences with the purpose front-loaded and the forceFetch behavior following immediately. There is no wasted text, and the structure is easy to parse.

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 synchronization tool with no annotations, no output schema, and an undocumented parameter schema, the description is incomplete. It does not clarify the core behavioral question of whether syncing fetches, applies, or both, nor does it explain the relationship with apply_zenmoney_diff, leaving the agent without enough context to call it confidently.

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 compensate. The sentence 'Можно запросить полную повторную загрузку выбранных сущностей' explains the intent of forceFetch as requesting a full re-download for selected entities, adding meaningful context beyond the bare enum. It does not explain individual enum values, but the enum names are largely self-descriptive entity types.

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 states a clear verb 'sync' and the target 'ZenMoney state via /v8/diff/', so an agent knows it synchronizes state. It does not explicitly distinguish itself from sibling apply_zenmoney_diff or explain whether it only fetches a diff versus applying changes, so it misses full sibling differentiation.

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 implied by the second sentence about requesting a full re-download of selected entities, which suggests when to use forceFetch. However, there is no explicit guidance on when to choose this tool over apply_zenmoney_diff, get_zenmoney_entities, or other sync-related siblings, and no exclusions or prerequisites are given.

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