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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the description is not responsible for stating safety and mutability. Beyond that, it adds no behavioral context such as whether the result is full and paginated, whether a connectionRef is needed, or whether the list is restricted to a current company context.

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 one sentence, front-loaded, and has no padding. It is concise without being verbose; however, it is near the point of too-to for a schema with eight parameters and multiple related sibling tools.

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?

Given eight parameters, no output schema, and a huge sibling set that includes brc_list_cash_payments and brc_get_payment, one sentence is not enough. The description does not help with deciding payment versus cash_payment, connectionref usage, pagination semantics, or what data is actually returned.

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 only 50%, but the description contributes no parameter-level meaning at all. Top, page, skip, and pageSize remain undocumented in schema and in description, and no explanation is given for how those pagination parameters interact with each other. An agent would have to infer or experiment.

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 says 'Lists BRC payments,' which is a clear verb+behavior statement: it returns a list of payment records. It does not differentiate itself from the close sibling tool brc_list_cash_payments, so an agent could still be unable to choose between them.

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 alternation, no exclusion, and no condition. The description does not point to brc_get_payment for a single payment, brc_create_payment for creating one, or brc_list_cash_payments for cash payments, so the agent only learns what the tool itself does, not when it should be preferred.

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