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

Annotations already declare the safe read profile (readOnlyHint, destructiveHint false), so the bar is lower. The description still adds useful behavioral context: returned fields (name and type), the exclusion of balances/transactions, and the Cotlet API key access requirement. It does not discuss pagination, but the added context exceeds the annotation baseline.

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 purpose is front-loaded and every sentence carries information (purpose, return fields, sibling linkage, scope, auth). It is slightly longer than needed and sentence one is grammatically dense, but nothing is wasted.

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 zero-parameter, no-output-schema read tool with annotations covering safety, the description supplies return content, scope limits, and the auth prerequisite. It is essentially complete, with only minor gaps like pagination behavior.

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 takes zero parameters, so the baseline is 4. The description correctly implies this is an unfiltered list with no required input, adding no misleading parameter claims.

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 names a specific verb and resource ('Bank and cash accounts in Alegra') and adds the practical purpose ('with the ID needed to record a payment'). It distinguishes this list from siblings like alegra_list_payments by clarifying these are accounts a payment can be booked to, so an agent can pick it without opening the schema.

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?

It explicitly routes the agent to the downstream sibling ('Use bank_account_id from each item in record_payment') and scopes out other uses ('no balances or transactions'). It lacks an explicit when-not/alternative branch, but the record_payment linkage and scope note give clear usage context.

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