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

Annotations already supply readOnly=false, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds the intent to modify fields but doesn't disclose side effects such as what deactivating a template affects or whether any operation is irreversible; it neither contradicts nor significantly extends the annotations.

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 that names the resource and the three supported update operations with no filler or redundancy.

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 mutating tool with six parameters, no parameter descriptions, and no output schema, this description is too thin. It does not clarify which fields may be combined, what the response contains, or what consequences deactivating a pipeline template has, leaving an agent to infer essential call 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?

Schema description coverage is 0%, so the description must compensate. It maps 'rename', 're-describe', and 'toggle active' to name, description, and is_active, but it says nothing about required pipeline_id or the request_id/idempotency_key fields, and it doesn't state whether at least one field must be provided.

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?

Description uses a specific verb ('update') and resource ('pipeline template') and enumerates the exact operations: rename, re-describe, toggle active. This clearly differentiates it from related siblings like pipelines_create, pipelines_read, and pipelines_reorder_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 operation list implies when to use the tool (when changing name, description, or active flag), but it gives no explicit guidance on when not to use it or which alternative to prefer. It also doesn't clarify whether stage-level changes belong to pipelines_stages_update.

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