QueryOrderFromOpenApi

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

The description goes beyond the readOnlyHint and openWorldHint annotations by disclosing API Key authentication, ACL permission requirements, a 600/min rate limit, and the old endpoint path. This is useful operational behavior, though it doesn't address pagination or response behavior details.

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 primary purpose is front-loaded, and the bullets are compact and each adds useful operational info. Only the 'Old path' bullet is somewhat ancillary, so it's efficient but not maximally tight.

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 10 optional parameters, no output schema, and a large sibling set, the description is not complete enough for an agent to call the tool correctly: parameter meanings, response shape, and selection criteria vs. alternatives are missing. It provides auth/rate-limit context but not enough to fill those gaps.

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?

With 0% schema description coverage and 10 parameters, the description must compensate, but it only hints at pagination (limit/cursor/direction) and account data (accountType). It leaves type, exchangeStatus, coin fields, and time range parameters undocumented in the description.

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?

Description states a specific action ('Paginated query of conversion order list via OpenAPI') and a resource, with a clear scope (asset account and OBU account data). It doesn't differentiate from sibling order-query tools like QueryOrderByPage or ConvertHistoryQuery, so it misses the last bit for a 5.

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 phrase 'Paginated query of conversion order list via OpenAPI' and 'supports asset account and OBU account data' imply when the tool applies, and auth/rate-limit bullets add operational context. However, it never explicitly names alternatives or states when not to use this tool vs. the many sibling query tools.

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