register_artifact_pipeline

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the agent knows it mutates but does not destroy. The description adds a little context with 'existing immutable run artifacts', implying it does not modify artifacts. However, it doesn't disclose side effects, conflict behavior, or the non-idempotent nature, which is a significant gap for a write operation.

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, tight sentence with no fluff, but it under-specifies for the tool's complexity. It front-loads the core action but omits essential context, making it concise at the expense of informativeness.

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?

Despite the rich input schema and presence of an output schema, the description lacks context about prerequisites, workflow integration, or failure modes. It gives no sense of what happens if the pipeline is already registered or if artifacts are missing. The complexity of this tool demands a more complete description.

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 description provides no parameter-level meaning. The schema contains many nested fields (run_id, pipeline_name, stages, etc.) with only titles, and the description does not explain critical concepts like 'bounded ordered pipeline' or the stage status discriminator. The agent is left without sufficient semantic grounding.

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 uses a specific verb 'bind' and identifies the resource ('bounded ordered pipeline' to 'existing immutable run artifacts'). It is distinct from sibling tools, none of which register pipelines. However, 'bounded ordered pipeline' is jargon that is not elaborated, so it does not fully achieve a 5.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., artifacts must already exist) or exclusions, nor does it name any alternative tools for similar actions.

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