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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true. The description adds behavior the annotations cannot: which types reject the status filter and which types swap location for from/to_location. It does not describe pagination or response shape, but the schema covers the paging contract.

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 sentences, the resource and type enumeration are front-loaded, and the filter caveats follow. The long type list is dense but necessary for an 18-value enum; little waste overall.

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?

With 12 parameters, no output schema, and read-only annotations, the description covers all filter dimensions and the type-specific exceptions. It omits return shape, pagination behavior, and explicit sibling routing, which are modest gaps for an already well-annotated read tool.

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 earns above baseline because the status enum's schema text defers to the description ('see the tool description') for per-type validity, and the description actually supplies that mapping, plus the location substitution rule, which the schema only half-states.

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 ('any SOS transaction type'), then enumerates all 18 supported types and names the backing endpoint GET /api/v2/{type}. It is clear apart from the more specialized list_sales_orders and list_purchase_orders siblings, though it never explicitly says 'use this for mixed/other types, use the specific list tools for a single document type'.

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?

Explains filter semantics (status allowed values per type, location vs from_location/to_location for transfers/rentals) which is real when-to-use context. However, it gives no guidance on when to prefer this generic lister over the sibling list_sales_orders / list_purchase_orders / list_items tools, leaving that routing to inference.

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