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

No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it discloses nothing: not whether the call is read-only or mutating, whether it requires auth, what side effects or costs it incurs, or what the pipeline returns. An agent cannot predict the outcome of calling it.

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 short but that brevity comes from under-specification rather than efficiency; there is no front-loaded statement of what the tool returns or when to invoke it. Every useful detail is absent.

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 no annotations, no output schema, and a description that only names the pipeline, an agent has no information needed to invoke this correctly or interpret its result. Given the density of overlapping referral/balance siblings, this is materially inadequate.

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?

There is a single optional parameter, notification_message, and the schema documents it at 100% coverage, including its fallback-purpose and plain-text constraint. The description adds nothing about the parameter, but the baseline is 3 when the schema already does the explanatory work.

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 restates the tool name with the generic verb 'Run' and adds no information about what the pipeline does, what data it touches, or what kind of result it returns. It is a tautology rather than a statement of purpose, and it gives no basis to distinguish it from siblings such as get_referrals_and_overdrafts_balance or view_referrals.

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 indication of when to use this tool, when not to, or which sibling to prefer. The sibling list contains at least three closely related referral/balance tools, and the description offers nothing to route an agent between them.

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