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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety and mutability profile is covered. The description adds that a whole saved pipeline executes in one call and enumerates built-ins, useful context, but says nothing about error behavior, permissions, or how dry_run changes execution.

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?

Two sentences, front-loaded with the core action before the built-in reference list. No filler, though the parenthetical param lists are dense and could have been grouped more legibly.

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?

With an output schema present, return values need not be described, and the built-in catalog fills the biggest gap (what recipes exist and what they take). The missing pieces are the dry_run semantics and any contrast with run_pipeline, which are minor against the rest.

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?

The schema leaves the crucial 'params' object opaque (anyOf object/null with no properties), and the description compensates by enumerating each built-in recipe with its expected keys (url, max_tokens, contains, index, pattern). That is real meaning beyond the schema, though dry_run remains undocumented in both places.

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 and resource ('Run a saved pipeline in one call') and enumerates the built-in recipes an agent can run, so the operation is immediately understandable. It does not explicitly distinguish itself from the sibling run_pipeline, which likely runs ad-hoc pipelines, so sibling differentiation is only implied.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the alternatives (run_pipeline, invoke, save_recipe). The built-in listing hints that this is the path for common page operations, but the agent must infer that routing itself.

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