create_pipeline

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so safety framing is covered. The description adds two useful non-annotation traits: that it validates before creating and that it 'may copy source data' (a data-movement/cost implication). It still omits permission requirements, reversibility, and rate limits, so it adds some but not rich context.

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 short, front-loaded sentences with no filler; the core action leads. It is arguably too terse for a complex mutation tool, but the text itself is efficient and well-ordered.

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 destructive, open-world mutation tool with a deeply nested config and 0% schema description coverage, the two-sentence description is insufficient. The output schema means return values need not be covered, but the near-total absence of parameter and behavioral detail leaves significant 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 0% and the single 'config' parameter is a large nested CDCConfig object with many meaningful fields (do_initial_snapshot, table_mappings, snapshot tuning, etc.). The description mentions 'existing peers' and source-data copying but does not explain the config structure or any field semantics, leaving the heavy schema essentially undocumented.

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?

States a specific verb (create) and resource (CDC pipeline) and adds the prerequisite 'using existing peers', which helps distinguish it from sibling tools like validate_pipeline. However, it does not explicitly contrast itself with validate_pipeline or update_pipeline, so an agent must still infer the boundary.

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?

'using existing peers' implies a prerequisite (peers must already exist) but the description gives no explicit when-to-use vs when-not guidance, nor does it route the agent to validate_pipeline or update_pipeline. Usage is only implied.

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