run_delta_sync

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

No annotations provided so description carries full burden. It explains watermark usage and first-run behavior but lacks details on concurrency, error states, or side effects beyond migration.

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 focused sentences, no redundancy. Front-loaded with key behavior, earns its place with essential info.

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?

With 5 required params, no output schema, and no annotations, the description is too brief. Lacks details on return format, error handling, or post-run state, which are critical for a migration tool.

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?

Only 40% schema coverage (platform, watermark_key described). Description adds no parameter context for object_or_project, sn_table, staging_table, leaving the agent guessing their meaning.

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 it runs a delta sync migration using a watermark, contrasting with run_full_migration sibling. Specific verb (migrate) and resource (records that changed) with first-run behavior noted.

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?

No explicit when-to-use or when-not-to-use guidance. The first-run context is implied but no alternatives or exclusions are mentioned given siblings like run_full_migration.

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