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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful content about what the listing includes (stages and un-pipelined replied creators), which goes beyond annotations and clarifies the result scope. It does not contradict any annotation.

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, well-structured sentence that front-loads the key concept ('Your pipeline') and immediately specifies the stage ordering and additional inclusion. Every word earns its place with no redundancy.

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 no-parameter, read-only listing tool with annotations covering safety, the description sufficiently communicates what the output will contain (deals by stage and replied creators not in pipeline). It does not detail pagination, ordering, or output field structure, but with no output schema and a simple listing purpose, this is acceptable. Minor gap in not stating if the list is full details or summaries.

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 tool has zero parameters, so there is nothing for the description to elaborate on. Per the rubric, 0 params earns a baseline of 4. The description confirms the tool takes no input and simply lists the pipeline, which is consistent.

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 states a specific verb (list) and resource (deals in pipeline), and defines the exact scope: deals by stage plus replied creators not yet in pipeline. This clearly distinguishes it from siblings like list_creators or list_campaigns, so an agent can immediately understand what it returns.

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 description implies when to use it ('Your pipeline') but does not explicitly name alternatives or exclusions. However, given the tool's zero parameters and read-only nature, the intended use is fairly obvious from context. It lacks explicit 'use this instead of X' guidance but still gives a clear functional context.

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