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

Annotations already declare a safe read-only, non-destructive, closed-world operation, so the safety profile is covered. Beyond that, the description adds nothing: no pagination behavior, no default page size, no note that results are company-scoped, and no indication of how connectionRef/session rotation interacts with this listing call.

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 short sentence with no filler, but its brevity reflects under-specification rather than efficient communication. Nothing is front-loaded because nothing of substance is said.

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 an 8-parameter paginated list endpoint with no output schema and partial schema descriptions, the description is entirely inadequate. An agent cannot determine filtering rules, paging semantics, or the required connection/company context from it.

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?

With 8 parameters and only 50% schema description coverage, top, page, skip, and pageSize carry no documentation anywhere and the description does not compensate. It also fails to clarify the companyName requirement or the connectionRef reuse rule that the schema itself flags as important.

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' is essentially a restatement of the tool name and title, adding no scoping or distinguishing detail. It does not differentiate the tool from siblings such as brc_list_cash_payments, brc_batch_cash_receipts, or brc_get_cash_receipt, nor does it say what a 'cash receipt' is in this domain.

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 when-to-use guidance, no prerequisite (e.g., a prior brc_confirm_company_connection), and no mention of alternatives. The schema hints that connectionRef is normally supplied on later calls, but the description never states this context.

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