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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is a safe read, not what the response contains, not whether the optional notification_message triggers a fallback message on failure. The only hint about that fallback lives in the schema, not the description.

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?

One sentence with no waste, but it is under-specified rather than concise — the brevity comes from saying nothing, not from tight editing.

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?

The tool has zero required parameters and no output schema, so the description would need to explain what the bank list looks like and its role in the payout/bank-transfer family. It supplies none of that, leaving an agent with a name and no contract.

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 single parameter has full schema description coverage (100%) explaining its plain-text, no-template-syntax constraint, so the schema does the work. The description adds no meaning about when the follow-up reply would fail or how the message surfaces, which is the baseline-3 outcome for high-coverage schemas.

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_supported_banks pipeline" restates the tool name and adds the word "pipeline" instead of describing an outcome. It never says what a supported bank is, what is returned, or how it differs from siblings like list_bank_beneficiaries or resolve_bank_account.

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 alternative is named. An agent cannot tell whether this is a prerequisite for bank_transfer/create_payout or a standalone lookup, and no prerequisites or ordering are given.

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