sync_sources

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

With no annotations, the description carries the full burden and does disclose meaningful traits: bounded concurrency, failure isolation (partial failures don't abort everything), and post-sync contradiction discovery. It does not cover auth requirements, rate limits, what a partial failure returns, or whether the operation is idempotent — gaps for a batch mutation with no output schema.

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?

A single front-loaded sentence that packs the batch framing first and the behavioral traits after. Dense but not bloated; "failure isolation" and "unified" are slightly opaque adjectives rather than concrete detail.

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 batch tool taking an array of connector/input objects with no output schema and no annotations, the description explains the overall behavior but omits return semantics, error/partial-failure reporting, and how contradiction discovery results surface. 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 100%, so the baseline is 3. The description loosely echoes the concurrency ("bounded concurrency") and runDiscovery ("contradiction discovery") parameters, but adds no new format or constraint detail beyond the schema and says nothing about the per-source connector/input structure.

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 gives a clear verb+resource ("synchronizes multiple external sources") and the leading "Batch ingestion tool" label distinguishes it from the singular siblings like sync_source, sync_document, and sync_website. It does not name those alternatives directly, but "batch"/"multiple" makes the scope unambiguous.

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 only implied: an agent can infer this is for syncing several sources at once rather than one. There is no explicit when-to-use/when-not guidance, no statement of prerequisites, and no routing to the sibling single-source tools.

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