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

With no annotations, the description carries the full burden, and it does disclose two meaningful traits: the delete cascades to the schedule, and the removal is soft/reversible via pipeline_deleted_restore. That is real value beyond structured fields. Still missing are permission requirements, whether run history is preserved, and whether any confirmation or blocking behavior applies to a destructive 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?

One sentence, front-loaded with the action and scope, with the recovery hint in a compact parenthetical. No 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 single-param tool with no annotations and no output schema, the description covers scope and reversibility but omits operational prerequisites and side effects on runs/history. Adequate to call safely, not complete.

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% and the single parameter pipeline_id has no description in the schema, so the description would need to compensate. It does not mention the parameter at all, though 'pipeline_id' is unambiguous and required. Baseline 3 for a trivially inferable single identifier.

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 ('Delete') and resource ('a pipeline and its schedule'), and the cascade detail distinguishes it from schedule_delete, which only removes a schedule. The named sibling pipeline_deleted_restore further clarifies its place in the lifecycle. It does not explicitly contrast with pipeline_update or explain what a pipeline is, but the operation is unmistakable.

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 parenthetical names pipeline_deleted_restore as the recovery path, which implies 'use this when you intend a recoverable removal.' However, there are no preconditions stated (e.g. whether the pipeline must be stopped first, whether active runs are cancelled) and no explicit 'do not use when...' guidance.

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