list_recent_orders

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

Without annotations, the description describes the return structure adequately but does not disclose behavioral traits like ordering (presumably by date), side effects, or prerequisites (e.g., login required).

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?

Concise, front-loaded purpose, followed by clearly labeled Args and Returns sections with no wasted words.

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?

Given the output schema is described and only one parameter, the description is mostly complete but lacks mention of ordering or authentication requirements.

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 description adds 'Maximum number of orders to return' to the limit parameter, which is not present in the schema's title/type alone, fully explaining its meaning.

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 clearly states the verb 'list' and resource 'recent orders from the Tuma250 My Orders page', distinguishing it from siblings like get_order_details (single order) and other tools.

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 guidance on when to use this tool versus alternatives such as get_order_details for specific orders, or whether authentication via login is required.

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