list_user_orders

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

With no annotations provided, the description carries the full behavioral burden. 'List' conveys a read operation and the per-user scoping is disclosed, but nothing is said about pagination, permission requirements, or output behavior. The continuation parameter hints at paging but the description never confirms or explains it, leaving an incomplete behavioral picture.

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 with no wasted words. The verb, resource, and scope all appear in the first clause, making the purpose instantly readable.

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?

The presence of an output schema relieves the description of explaining return values, and the tool is structurally simple (2 params, 1 required). However, the continuation semantics and pagination behavior are undocumented, and no guidance distinguishes this from the sibling order-listing tools, leaving minor but real gaps.

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 0%, so the description must compensate. The phrase 'made by a specific user account' adds meaning to user_id, but the continuation parameter is entirely unexplained — an agent cannot infer it is a pagination cursor from either the schema or the description. Coverage of parameters is incomplete.

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'), a concrete resource ('ticket purchase orders'), and a scope ('by a specific user account') that maps to the user_id parameter. It is distinguishable from siblings like list_event_orders and list_organization_orders through the per-user phrasing, though it never names those alternatives explicitly.

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?

The scope phrase implies this is the tool for retrieving one user's orders, providing clear context. However, it offers no explicit exclusions or alternative routing, which is a genuine gap given the three near-identical list-order siblings (list_event_orders, list_organization_orders, get_order) that an agent must choose among.

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