gp_run_pipeline

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It does not mention possible side effects, duration, idempotency, or return value. 'Executes the entire pipeline' is vague and omits crucial traits like whether it triggers a long-running process or modifies state.

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 description is a single, efficient sentence with no redundant words. However, it could be slightly expanded to improve completeness without harming conciseness.

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?

Given the complexity of a pipeline tool with no annotations or output schema, the description is insufficient. It does not explain that the pipeline may involve multiple steps or how the output relates to individual tool results. More context is needed for agents to use it reliably.

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 sole parameter 'goal' is well-described in the schema with an example. The description adds no extra parameter information. With 100% schema coverage, the baseline score of 3 is appropriate.

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?

The description clearly states the verb ('executes'), the object ('entire GrowthPilot lead generation campaign pipeline'), and the scope ('end-to-end for a given user goal'). It distinguishes this tool from sibling tools which handle individual steps like planning or discovery.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not clarify that this should be used after setting a goal, or that individual steps might be preferred for inspection. The agent receives no hints about its role relative to siblings.

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