QueryOrderFromOpenApi

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

With no annotations, the description carries the full burden. It discloses authentication (API Key), ACL permissions, rate limit, and the old API path. However, it omits details about pagination behavior, default parameter values, and response format.

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 five bullet points, front-loading the purpose. It could be more structured by separating parameter details, but the current format is efficient and scannable.

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 tool with 10 optional parameters, no output schema, and no annotations, the description is insufficient. It lacks explanation of pagination, parameter roles, and return values, leaving significant gaps for successful usage.

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%, so the description must explain parameters. It mentions 'paginated query' and support for asset/OBU accounts but does not map these to specific parameters (cursor, limit, accountType). Most parameters remain unexplained.

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 that the tool performs a 'paginated query of conversion order list via OpenAPI', identifying the specific resource and action. However, it does not differentiate itself from the sibling 'QueryOrderByPage', which appears to serve a similar purpose.

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 description provides no guidance on when to use this tool versus alternatives. It lists authentication and rate limit details but does not contextualize usage in relation to similar query tools such as getOrderList or QueryOrderByPage.

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