sync_data_product_to_atlas

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

No annotations are provided, so the description carries full burden. It explicitly flags the operation as a '**WRITE OPERATION**' and explains the conditional linking behavior based on atlas_qualified_name. However, it doesn't disclose what happens to existing entities (overwrite vs skip), auth requirements, or side effects of syncing all products.

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 compact with two sentences plus an argument list. The bold WRITE OPERATION flag is a useful front-loaded visual. The Args section is a slightly informal addition but does not waste space.

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?

Both parameters are documented with behavior. An output schema exists, so return-value explanation isn't needed. For a sync/write tool, it covers the core semantics (optional filtering, conditional linking) reasonably well, though it skips details about repeated syncs and error handling.

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 coverage is 0%, so the description must compensate. It explains product_id semantics ('Optional product ID. If omitted, syncs all local marketplace products') and link_dataset conditionally ('when atlas_qualified_name is set'), which adds meaning beyond the bare schema. However, it doesn't specify allowed values or formats for product_id, leaving partial ambiguity.

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 verb ('Sync') and resource ('marketplace product(s) to Atlas as data_marketplace_product entities'). It distinguishes itself from read-oriented siblings like search_data_products and get_data_product by marking '**WRITE 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 explains behavior when product_id is omitted ('syncs all local marketplace products') and when link_dataset is set, but provides no explicit when-to-use guidance or exclusions relative to siblings like ensure_data_marketplace_typedef or publish_data_product. Context is implied rather than stated.

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