Get Pipeline Info

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

With no annotations provided, the description carries the full behavioral burden, yet it adds nothing beyond restating the purpose. It does not clarify that this is a zero-side-effect read/introspection call, nor what kind of metadata or tool enumeration is returned; the only hint of behavior is the phrase 'available MCP tools'.

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?

A single front-loaded sentence with zero waste. The resource and scope are stated immediately and nothing requires trimming.

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 zero-parameter introspection tool with an output schema already covering return values, the description is nearly sufficient. What is missing is the invocation context (when in an agent's workflow this discovery call is appropriate).

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 tool takes no parameters, so there is no parameter semantics to document; the 4 baseline applies. The description correctly does not fabricate inputs.

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 ('Get') and resource ('metadata about the Champollion pipeline and available MCP tools'), which is more than a restatement of the name. It is distinguishable from the start_* siblings and job-management siblings, though it never explicitly contrasts itself with get_job_status or list_jobs.

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 call this versus alternatives. Nothing tells the agent whether this should be invoked at the start of a session, when a pipeline name is unknown, or how it relates to get_job_status and list_jobs in the sibling set.

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