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

The description adds no behavioral information beyond the annotations. Annotations already indicate read-only, non-destructive behavior; the description merely restates the tool's purpose and says nothing about pagination, filtering, or the return format.

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 brief and not bloated, but it is also terse to the point of under-specification. One sentence can still be useful; here the sentence restates the tool title without offering additional context, so it is minimally acceptable but not strong.

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 large family of similar list tools, the description is not enough for an agent to confidently know when to this tool, how results are paginated, or what data is returned. The schema and annotations carry most of the meaning.

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 covers only 50% of parameters with descriptions, but the tool description provides no parameter context whatsoever. it does not explain pagination fields (top, page, skip, pageSize) or clarify how companyName and connectionRef work together.

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 uses a clear verb and resource: 'Lists BRC sales entries.' This tells an agent the tool retrieves a sales-entry collection, but it does not differentiate from sibling tools like brc_list_sales, brc_list_sales_invoices, or brc_list_sales_credit_notes.

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 guidance about when to use this tool, what company context is required, or how it relates to the many sibling list tools. No alternatives are named and no exclusions described.

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