QueryOrderByPage

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

No annotations are provided, so the description carries full burden. It mentions authentication, permissions, and rate limit, but does not explicitly state if the operation is read-only or describe side effects. Since it's a query, it's likely safe, but the description could be more explicit about behavior.

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 well-organized with a main sentence followed by bullet points for key details. It is front-loaded with the purpose and provides useful context without unnecessary words.

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?

No output schema is provided, and the description does not explain what the response contains (e.g., list of orders). Parameters are not documented. The description lacks completeness for a paginated query tool.

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 input schema has 4 parameters (cursor, limit, toCoin, fromCoin) with 0% description coverage. The description only mentions 'cursor pagination' but does not explain any parameter's meaning or usage. This is a critical gap.

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 aggregates asset and OBU account data and queries conversion history orders by cursor pagination. It specifies the resource ('conversion history orders') and the operation ('query' with pagination), distinguishing it from other query tools like QueryOrderFromOpenApi.

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 authentication requirements (API Key), ACL permission, and rate limit. It implicitly defines when to use (for conversion history queries) but does not explicitly exclude alternatives or compare with sibling tools.

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