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

Adds substantial context beyond annotations: idempotencyKey retry returns the first result, admin-only authorization, no external service calls, no side effects on stages, and a strict confirmation protocol. The destructiveHint/readOnlyHint/idempotentHint annotations are all corroborated rather than merely restated.

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?

Core purpose is front-loaded and the safety instructions are warranted for a destructive mutation. It is verbose, with some repetition around never inferring consent, but nearly every sentence carries operational weight rather than filler.

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 destructive, admin-only mutation with no output schema, the definition covers the critical gaps: authorization, confirmation protocol, idempotency, scope boundaries, and where ids come from. An agent has everything needed to call it safely.

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 coverage is only 17%, so the description must compensate and largely does: it explains id comes from get_pipeline_summary, name is a rename, and isDefault semantics (steals default from the current holder). Weaknesses: the required 'confirm' boolean and the workspaceId parameter are not explicitly explained in the description text.

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 specific verbs and resource scope: 'Renames one pipeline, or makes it the default for its type.' It also explicitly disambiguates from sibling tools by saying it never touches stages and pointing to add_pipeline_stage/update_pipeline_stage and workspace pipeline settings for removal.

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?

Gives explicit when/when-not guidance: only workspace admins may call it, it is a rare admin change, and stage edits must go elsewhere because removing a stage moves records. The confirmation precondition and the 'ask instead of calling' rule are directly actionable.

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