resync_pipeline

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly warns that drop_and_load=true is destructive (drops tables) and that the default false preserves and updates differences. This highlights the key risk of the tool.

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 two sentences long, front-loads the core action, and is entirely free of filler. Every sentence adds essential information about the resync behavior and its destructive alternative.

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 simplicity (2 params, no output schema, no annotations), the description covers the main behavioral difference and default mode. It lacks details like return values or preconditions, but those are less critical for this straightforward mutation tool. The description is reasonably complete for an agent to decide and invoke it correctly.

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 covers drop_and_load with a description, but pipeline_id has no schema description. The tool description implies pipeline_id identifies the pipeline to resync ('Resync a pipeline'), which provides context. Overall, the description adds moderate value beyond the schema, but does not fully compensate for the undocumented pipeline_id semantics.

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 identifies the action ('Resync a pipeline by restarting its historical load') with a specific verb and resource. It distinguishes itself from sibling tools like list_pipelines, create_pipeline, and update_pipeline_config by focusing on the resync operation.

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 clarifies when to use the tool by explaining the two modes: destructive (drop_and_load=true) and non-destructive (default). It doesn't explicitly state alternatives, but the unique operation and sibling names imply it is the correct tool for resyncing a pipeline, not for general CRUD or config updates.

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