airbyte_trigger_sync

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

The description explains that reset clears destination data and causes downtime, while sync does not. It states the return value (newly created job with jobId and initial status). Annotations already indicate readOnlyHint=false, and the description adds behavioral context beyond that.

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 well-structured with clear sections, examples, and warnings. Every sentence adds value; there is no redundancy or fluff.

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 tool's complexity (two job types, comparison to refresh), the description is very complete. It covers when to use, when not to use, behavioral effects, and return value. The presence of an output schema means return format details are already handled.

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?

Although the input schema provides descriptions for job_type and connection_id, the description adds meaning by explaining the difference between sync and reset, and provides examples showing how to pass the parameters. The 'When NOT to Use' section also clarifies the job_type parameter's role in deciding between reset and refresh.

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 triggers a sync or reset job for a connection. It distinguishes between sync and reset, and also differentiates from the sibling tool airbyte_trigger_refresh, which is used for non-destructive refreshes.

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 includes explicit 'When to Use' and 'When NOT to Use' sections. It advises against using when the connection is already running (and suggests checking with airbyte_list_jobs) and recommends airbyte_trigger_refresh for non-destructive refreshes instead of reset.

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