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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not whether this is a read or a write, whether calling it has side effects ("run a pipeline" could imply processing work), nor whether it requires auth. For a tool whose name suggests fetching a balance, the absence of any indication of cost or consequences is a serious gap.

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?

It is one short sentence, but it is under-specified rather than concise: it is front-loaded with a restatement of the name and carries no information an agent could act on. Brevity here stems from omission, not economy.

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?

There are no annotations and no output schema, so the description must supply safety profile, expected return, and usage context — it supplies none of these. An agent cannot tell whether this is a safe read or a state-changing operation, nor what it gets back.

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?

Schema description coverage is 100% — the single optional notification_message parameter is fully documented in the schema. The description adds nothing about the parameter, but per the baseline rule for high coverage, 3 is the correct score.

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?

"Run the get_referrals_and_overdrafts_balance pipeline" only restates the tool name in other words; the verb "run" and noun "pipeline" add no resource or outcome information. There is no differentiation from siblings like view_referrals, get_additional_referrals_and_balances, or list_ngn_money_movements_and_overdraft_data, which plausibly overlap in scope.

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 when-to-use, when-not-to-use, or prerequisite information is given. An agent facing view_referrals, get_additional_referrals_and_balances, and this tool has no basis in the description for choosing among them.

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