ps_run_pipeline

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

With no annotations, the description carries the entire behavioral burden, and it discloses only the internal stage ordering. It says nothing about side effects, despite a save_to_periscope_data parameter defaulting to false that implies an optional write, nor about runtime, external calls, idempotency, or permissions.

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?

The single sentence is front-loaded and free of waste, but it is under-specified rather than concise for a nine-parameter pipeline tool with no annotations. Its brevity leaves the agent guessing on nearly every invocation detail.

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?

An output schema exists, so return values need not be described, but for a nine-parameter orchestrator with zero parameter documentation and no annotations the definition is materially incomplete. Side effects and defaults around persistence (save_to_periscope_data) go entirely unexplained.

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?

Nine parameters with 0% schema description coverage receive no explanation whatsoever in the description. Only 'enrich' is loosely echoed by the stage list, and nothing clarifies hours, threshold, sources, languages, config_path, topic_dedup, periscope_path, or save_to_periscope_data, so the description fails to compensate for the coverage gap.

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?

Names a specific verb ('Run') and enumerates the composite stages (fetch, score, filter, enrich, summarize), which map cleanly onto sibling tools like ps_fetch_items, ps_score_items, ps_filter_items, ps_enrich_items, and ps_generate_summary. The phrase 'in one call' implicitly distinguishes it from running those stages individually, though it never says so outright.

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 guidance or named alternative; the only cue is 'in one call,' which implies this is the batched shortcut for the individual stage tools. An agent can infer the intent but must guess at prerequisites, cost, or when the single-stage tools are preferable.

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