etl_design_pipeline

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says the tool 'designs' a pipeline, but does not reveal whether it writes files, returns a plan, requires authentication, or has side effects. The api_key parameter hints at authentication, but the description does not explain its role or consequences.

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 a single efficient sentence with no wasted words and places the core concept first. It could include more useful context, but it is appropriately concise for a simple declarative purpose statement.

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?

The description is too thin to be fully actionable on its own. There is no output schema, so the agent is not told what 'design' produces, what format to expect, or how the pipeline design is delivered. Combined with the lack of usage guidance and behavioral transparency, the tool remains under-specified for correct invocation in ambiguous contexts.

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 100%, so the structured schema already documents all four parameters adequately. The description adds minimal parameter-level meaning, only indirectly implying source_type and destination map to source and load stages. This meets the baseline for high schema coverage without adding significant new insight.

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 names the verb 'Design' and the resource 'ETL/ELT pipeline', and adds the scope 'source, transform, and load stages.' This is specific enough to convey the core action, though it does not explicitly distinguish the tool from closely related siblings like etl_generate_transforms or pipeline_generate.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools such as etl_generate_transforms, etl_schedule_setup, and pipeline_generate suggest overlapping contexts, but the description offers no conditions, exclusions, or references to help an agent choose correctly.

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