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

Annotations already declare readOnlyHint=true, so safety is covered; the description still adds useful behavioral context by disclosing the response shape (JSON:API data, attributes, relationships, pagination metadata) and the exact endpoint. It does not mention rate limits or filter failure behavior, a minor gap.

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?

Three short sentences with the core purpose front-loaded and no filler. Slight redundancy between 'Read-only' and the surrounding annotation, but it earns its place for agents that read only the description.

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?

No output schema exists, so the description's note about JSON:API data/attributes/relationships/pagination is exactly what an agent needs to interpret results. Parameters are fully covered by the schema; only filtering semantics specific to series are missing.

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 100% with all three params (page, page_size, filters) fully documented in the schema. The description adds no parameter-specific meaning, so baseline 3 applies; notably the filters examples are customer/product/document oriented rather than series-specific.

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?

States a specific verb (List) and resource (document series) scoped to the connected company, and names the underlying endpoint. It doesn't explicitly contrast with the many sibling list_* tools, but the resource is unambiguous.

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 indication of when to use this versus alternatives like toconline_list_sales_documents, nor any prerequisites or exclusions. The only usage-adjacent text is 'Read-only', which is a safety statement, not selection guidance.

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