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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally, but the description adds zero behavioral context beyond that. It does not mention that results are paginated (top/page/pageSize), that it supports OData-style filter/orderBy, that it requires an established company connection, or what the response shape looks like. For an 8-parameter list endpoint this is a notable gap, even with annotations lowering the 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 description is a single short sentence that front-loads the main action, which keeps it efficient. However, it borders on restating the name, so its brevity is a sign of under-specification rather than well-edited content. Every sentence scores the place, but there should have been more sentences.

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 list tool with 8 parameters, no output schema, and no description of return values, the definition is not complete enough for an agent to confidently determine what it will receive or how to page through results. It does not link this operation to related tools such as brc_get_cash_receipt or brc_confirm_company_connection, relying entirely on the connectionRef parameter description to carry the stateful-context. The description leaves pagination behavior, filtering semantics, and exit conditions unstated.

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 50%, and the description contributes nothing to the un-described parameters: top, page, skip, and pageSize have no schema descriptions, and the one-line description does not hint that these are pagination controls. The schema does document companyName, connectionRef, filter, and orderBy (the latter two hedged as 'only if this endpoint supports...'), but the description itself adds no parameter meaning. At 50% coverage and zero description support for the undocumented half, the tool fails to compensate.

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 'Lists BRC cash receipts' clearly states a specific verb ('lists') and a specific resource ('cash receipts'), so an agent can tell it fetches a collection rather than creating, getting, or deleting one. It does not, however, explicitly differentiate itself from sibling tools like brc_list_cash_payments or brc_batch_cash_receipts, leaning on the noun and naming convention to do that work. It reads close to the title 'List Cash Receipts' and lacks a sibling-discriminating phrase, so it stops short of 5.

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 guidance is given about when to use this tool instead of brc_list_cash_payments, brc_get_cash_receipt, or brc_batch_cash_receipts. There is no mention of pagination strategy, company-connection prerequisites, or any conditions that would make this the right choice. The description carries no context beyond the name itself.

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