getAllOrders

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

Discloses default 90-day range and 180-day maximum, which is valuable. However, with no annotations and 0% schema coverage, the description fails to mention important behavior like pagination (page/size are required), ordering, or output structure, leaving significant gaps.

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 concise with two sentences that front-load the core action. However, it could be more structured to include parameter hints without becoming verbose.

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 tool's 7 parameters, no output schema, and many sibling order-list tools, the description is notably incomplete. It lacks parameter guidance, pagination details, differentiation from similar tools, and output format, leaving the agent with insufficient information to use the tool effectively.

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%, yet the description does not explain any of the 7 parameters. It only implies time-range parameters through the default mention, but required page/size and other filters (status, tokenId, side) are completely undocumented.

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 it retrieves a list of P2P orders with a verb and resource. It specifies default and maximum time ranges, which adds context, but does not explicitly differentiate from sibling tools like getOrderList or getOrderHistory.

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 explicit guidance on when to use this tool versus alternatives. The description only states what it does without providing context for selection among many similar order-listing tools.

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