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

With no annotations provided, the description carries the full burden but discloses nothing about pagination, ordering of results, authentication, or return shape. 'Your orders' implies a caller-scoped list, but even that scoping is left implicit.

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?

It is a single short sentence with no waste, but the brevity comes at the cost of under-specification rather than tight editing. There is nothing front-loaded beyond the resource name.

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 listing tool with no output schema, no annotations, and 0% schema description coverage, the description should at minimum say what is returned and how results are scoped or paged. None of that is present.

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 single role parameter is an enum (buyer/seller) that documents itself, and the phrase 'as buyer or seller' loosely maps to it. However, the description adds no semantics about what the role selection changes, such as whether results are purchases versus sales.

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 phrase 'Your orders as buyer or seller' identifies the resource (the caller's orders) but supplies no verb, so it is unclear whether this lists, counts, or summarizes them. It also fails to distinguish itself from the sibling get_order, which presumably retrieves a single order.

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?

There is no statement of when to use this tool versus get_order, cancel_order, or payment_collect, and no prerequisites or conditions are given. The agent must infer usage purely from the name.

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