start_pipeline

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

It mentions that the pipeline runs sequentially and returns a job_id immediately, indicating async behavior. However, no annotations are provided, so the description carries the full burden but lacks details on resource usage, prerequisites, or effects.

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 concise (one sentence) but too brief for the tool's complexity. It could list key parameters or stages.

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 high parameter count, many required, and numerous sibling tools, the description is incomplete. It lacks explanation of pipeline stages, parameter dependencies, and output schema details.

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?

With 18 parameters, 11 required, and 0% schema description coverage, the description provides no explanation of any parameter. This is a major gap for correct invocation.

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 launches the full Champollion pipeline (all 6 stages sequentially) and returns a job ID. This distinguishes it from sibling tools that launch individual stages.

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 implies usage for running the full pipeline, but does not explicitly state when to use vs alternatives like start_cortical_tiles or start_training. No guidance on when not to use.

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