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

Annotations already declare readOnlyHint=true and destructiveHint=false, lowering the bar. The description adds meaningful context: the recommendations are 'persisted,' scoped to the authenticated business, and no side-effectful operations are performed. This goes beyond the bare 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?

A single, front-loaded sentence that conveys scope, target, and non-behaviors without any fluff. Every word contributes to the agent's understanding.

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 read-only listing tool with fully documented optional parameters and safety annotations, the description is nearly complete. It could be slightly stronger by naming a sibling for mutation flows or describing the result shape, but no output schema makes that less critical.

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?

All five parameters are fully documented in the schema with descriptions and defaults, so the description does not need to repeat them. The description itself says nothing about parameters, which is acceptable because the schema carries the full semantic weight.

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 ('Lists'), a specific resource ('persisted pipeline recommendations'), and a clear scope ('for the authenticated business'). It also explicitly differentiates the tool from any mutation-oriented pipeline tool by listing what it does not do.

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 clearly communicates that this is for read-only listing and explicitly excludes generating, editing, approving, rejecting, or executing recommendations. It does not name a specific alternative tool, but the context makes when-to-use reasonably clear.

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