my_orders

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

With no annotations supplied, the description carries the full behavioral burden; it does disclose the authentication requirement and the result ordering, which are genuinely useful beyond structured fields. It says nothing about what an unauthenticated call does, how pagination behaves by default, or what 'full' changes, leaving the mutation-free read profile only implied.

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 short sentences with no filler, and the core fact (order history, newest first) is front-loaded. The phrasing is efficient, though the first fragment lacks a verb, which costs a bit of clarity for essentially no length savings.

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?

An output schema exists, so return values need not be described, but for an authenticated listing tool with three undocumented parameters and no annotations, the definition is too thin. It should at least explain 'full' and the paging defaults to let an agent call it correctly on the first attempt.

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% for all three parameters (full, page, page_size), and the description says nothing about any of them. 'Newest first' gestures at ordering but does not explain paging or what the boolean 'full' flag expands, so the agent is left guessing at parameter 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 identifies the resource ('Your online orders') and its ordering ('newest first'), which is enough to know it returns a list of the caller's order history. It never distinguishes itself from close siblings like my_products, last_order, or order_detail, and the action verb (list) is only implied rather than stated.

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?

'Requires login' gives a concrete prerequisite, and 'newest first' hints at the typical use case of browsing recent order history. However there is no explicit guidance on when to pick this tool over last_order (single most recent order) or order_detail (one order's contents), so the agent must infer the boundary from names alone.

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