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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds real context beyond that: results are scoped to API-balance orders, sorted newest first, and incur no charge. It says nothing about pagination limits or how many orders come back, which matters for a listing tool.

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 the scope and ordering front-loaded. 'Free' as a fragment is slightly cryptic, but nothing is padded or redundant.

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 minimal single-parameter read tool with no output schema, the description covers what the list contains and its order. It falls short on the two things an agent still needs: the meaning of 'before' and any sense of result volume or paging.

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 coverage is 0% and the single parameter 'before' (integer, minimum 1) is never explained. The description's 'newest first' gestures at ordering but does not clarify that 'before' is a paging cursor or what the integer refers to, leaving the only parameter ambiguous.

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?

Names the resource (orders), the scope (this account's, paid from API balance) and the ordering (newest first), which is enough to tell it apart from get_order (single order) and order (create). It reads as a specific listing tool rather than a tautology, though the verb 'list' is only implied by the name.

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 explicit statement of when to use this versus get_order or order, and no preconditions. The only indirect signal is 'Free', which hints at cost rather than at selection between alternatives.

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