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

With no annotations, the description carries the burden and does disclose key side effects: the id is preserved, the pipeline comes back disabled, and the inbound trigger URL changes. It still omits error conditions (e.g., no snapshot available), permission requirements, and whether the original trigger URL is permanently invalidated.

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?

One dense sentence, front-loaded with the action and immediately followed by the concrete outcomes. No filler or redundant restatement of the tool name.

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 single-parameter tool with no annotations or output schema, the description covers the important behavioral facts (id reuse, disabled state, new URL). Only edge cases and failure modes are missing.

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 0% for the single param, so the description must compensate. 'Same id' hints that pipeline_id refers to the deleted pipeline's identifier, but it never explicitly says which pipeline_id to supply, leaving a small ambiguity about whether the caller passes the deleted pipeline's id.

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 ('Re-create'), resource ('deleted pipeline') and source ('from its last snapshot'), which cleanly distinguishes it from pipeline_create and pipeline_history_restore. The parenthetical adds concrete outcomes (same id, disabled, new URL) so the agent knows exactly what it gets.

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 word 'deleted' implies the precondition (only for pipelines that were deleted), but there is no explicit when-to-use statement and no mention of alternatives such as pipeline_create or pipeline_history_restore. Usage must be inferred from the resource name.

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