get_orders

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

With no annotations provided, the description carries the full burden of disclosing behavior. It adds that the listing is scoped to the authenticated user, which is helpful, but it does not mention read-only nature, pagination, sorting, or response shape. This leaves significant behavioral traits undisclosed for a list operation.

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 six words long with no filler. It front-loads the core operation and resource, making it easy to parse.

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 tool has seven parameters, no output schema, and no annotations, yet the description only states the basic listing operation. It omits any information about filtering, sorting, pagination, or what distinguishes an order from other marketplace resources, making it incomplete for an agent that needs to call it correctly.

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% and the description contributes nothing about the seven parameters. The description does not explain the meaning of page, sort, status, perPage, sortOrder, createdAfter, or createdBefore, and it makes no attempt to compensate for the schema's lack of descriptions.

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 states a specific verb ('List') and a clear resource ('authenticated marketplace purchases and sales'), which distinguishes it from both the singular get_order and the collection/wantlist listing siblings. However, it does not explicitly name any sibling or state what it is not, so it stops short of a perfect score.

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 'authenticated marketplace purchases and sales' implies when the tool is appropriate (listing the user's own orders) and implicitly differentiates from get_order (single order), but it never states alternatives or exclusions. There is no explicit 'use this instead of X' guidance, so the usage context is only implied.

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