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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the return payload hint ("with totals and status") and the underlying endpoint POST /Document/DocumentGet, which is meaningful because no output schema exists to describe results; it still says nothing about permissions or result volume limits.

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?

Two tight sentences, front-loaded with the purpose and followed by the narrowing options, with the endpoint tucked at the end. Only the trailing "and so on" is mild filler; nothing else could be cut without losing information.

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 a zero-required-parameter list tool with an output-schema-free surface, the description covers what it returns (documents with totals and status) and how to narrow broadly enough to invoke it correctly. Pagination and "newest first" behavior are handled by the limit parameter description rather than here, and permission prerequisites remain unaddressed.

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%, so the baseline is 3, but the description adds value beyond it by naming three of the five parameters in natural language and explicitly linking document_type_ids to the sibling lookup tool that supplies valid ids. It omits any mention of the limit/filters parameters, which is acceptable since the schema documents them thoroughly.

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 and resource ("List transaction documents") and immediately bounds the scope with "of any type", enumerating shipments, invoices, receipts, credit notes, returns and adjustments. That scope word is what separates it from the typed siblings list_sales_orders, list_purchase_orders and list_work_orders, which an agent can distinguish without opening either schema.

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?

Gives concrete narrowing paths — document type ids, document number, status — and routes the agent to megaventory_list_document_types to obtain the type ids. It does not state when to prefer this general lister over the order-specific siblings, so there is a small residual ambiguity about which tool to pick for sales orders or purchase orders.

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