List your recent orders

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

With no annotations provided, the description carries full behavioral disclosure. It states the result limit (up to 50) and ordering (newest first), which are key behavioral traits. It does not mention authentication or side effects, but the operation is clearly a read-only list.

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?

The description is a single sentence with no filler. Every word adds value: the cap (50), the scope (your recent orders), and the ordering (newest first).

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 simple zero-parameter, read-only list endpoint without an output schema, the description covers the essential details needed to invoke it correctly. It could mention how to retrieve older orders beyond the first 50, but that is a minor gap for such a minimal API.

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?

The tool has zero parameters, so the schema is already complete. The description's 'your recent orders' implies an authenticated-user context, which is sufficient. No parameter-level gaps exist to compensate for.

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 uses a specific verb and resource: 'Returns up to 50 of your most recent orders, newest first.' It clearly distinguishes this history-listing tool from siblings like get_order (which fetches a single order) and list_categories or search_catalog.

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 context is implied by the title 'List your recent orders' and the description, but there is no explicit when-to-use or alternative guidance. An agent has to infer that this is the right tool for browsing recent orders rather than using get_order or search_catalog.

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