execute_pipeline

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

No annotations are provided, so the description must carry the full burden. It describes the input format and options but omits behavioral traits such as resource usage, side effects, error conditions, or execution guarantees.

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 well-structured with an example and bullet-like lists, making it readable. It is slightly lengthy but every sentence adds value, though some repetition (e.g., listing filters) could be slightly more compact.

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 complexity, the description covers the pipeline structure, available filters, and output types comprehensively. However, it lacks details on error handling, prerequisites, or performance implications, leaving minor 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?

The schema provides minimal description ('Complete PipelineDefinition as JSON dict'), but the description enriches it with a full JSON example, valid filters list, and output types, adding substantial meaning beyond the schema.

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 'Execute a custom pipeline definition (advanced)' and specifies it's for 'CFD/FEA/CAE specialist agents.' It lists available filters and output types, distinguishing it from single-step sibling tools like clip or slice.

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 identifies this as the primary interface for specialist agents, implying use for complex pipelines. It implicitly contrasts with simpler sibling tools but does not explicitly state when not to use it or alternative tools.

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