sync_accounts_to_customers

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

The description discloses that the tool 'creates or updates customer records', which is a key behavioral trait and aligns with the schema's idempotentHint. However, with no tool-level annotations provided, the description carries the burden of transparency. It does not mention matching logic, potential side effects beyond create/update, error handling, or reversibility, leaving some uncertainty.

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 concise—two sentences plus a compact example. It front-loads the core action and direction, then provides a concrete usage example. Every sentence earns its place, with no wasted words.

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 sync operation with three parameters and no output schema, the description is largely complete: it states the direction, the create/update behavior, and includes a practical example. It could mention matching criteria or failure modes, but the schema plus description cover the essentials. The complexity is moderate, so a 4 is appropriate.

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 input schema already provides 100% coverage with descriptive text for each parameter, including enums for source_module and target_module. The description adds a small example JSON that illustrates usage (e.g., filters.limit), but it does not add deeper semantic meaning beyond what the schema already offers. Baseline 3 is appropriate.

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 tool's function: 'Sync CRM accounts to Books customers' with an explicit direction (CRM → Books). This distinguishes it from sibling tools like sync_contacts_to_customers and sync_customers_to_contacts. The example further reinforces the specific source and target modules.

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 explicitly notes the CRM → Books direction, which helps an agent understand when to use this tool (for account-to-customer syncs). However, it does not explicitly name alternative tools or provide exclusions (e.g., 'use this instead of sync_contacts_to_customers when source is accounts'). The direction is clear, but guidance is not exhaustive.

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