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

Annotations already cover read-only, non-destructive, and open-world behavior, so the bar is lower. The description adds real value beyond that: the response is JSON, it contains four named transaction categories, and pagination caps at 25,000 lines per page, which tells the agent to expect to page through large invoices. It does not describe error or auth behavior, so it is not a 5.

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?

A single front-loaded sentence lists the payload contents first, then format and page limit, followed by the endpoint. Every clause earns its place and nothing is repeated from the schema or annotations.

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?

There is no output schema, so the description correctly states the return format and what the payload contains, and it discloses the pagination ceiling. It leaves the shape of individual transaction line items unspecified, a minor gap for a read tool whose annotations already declare safety.

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 coverage is 100%, so baseline is 3. The description adds meaning for the page parameter by stating the 25,000-line page cap, complementing the schema's guidance to use the previous reply's next_page. It says nothing about the invoice_id format beyond what the schema's pattern already provides.

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-resource pair: it returns the transactions (sales, commissions, shipping, returns) behind one bol invoice, in JSON, along with the exact endpoint. An agent can distinguish it from list-style siblings like bol_list_invoices by the required invoice id. It stops short of naming an alternative tool, which keeps it at 4 rather than 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?

Usage is only implied: an agent deduces that this tool is called for a single invoice's line-level detail. There is no explicit when-to-use, when-not-to-use, or routing to bol_list_invoices or bol_get_commissions. Adequate minimum viability, but nothing to guide selection among 17 siblings.

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