query_orders

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

No annotations are provided, so the description carries full burden. It states the tool is a lookup operation but does not disclose behavior when txids are invalid, whether it is read-only, any authentication requirements, or rate limits. The optional parameters (trades, userref, consolidate_taker) are not mentioned, leaving gaps in behavioral understanding.

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 a single, front-loaded sentence that conveys the essential information (verb, resource, parameter, limit) without any extraneous words. Every part is necessary.

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 4 parameters, no output schema, and no annotations, the description is too sparse. It covers only the txid parameter and the 50-limit constraint, omitting the optional parameters and their impact on results. There is no description of the return data or error handling, leaving the tool incomplete for an agent.

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%, meaning the description must explain parameters. It only references the required 'txid' (transaction id) without specifying format or constraints. The three optional parameters (trades, userref, consolidate_taker) are not described at all, so the description adds minimal meaning beyond the schema.

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 specifies 'Look up specific orders by transaction id (up to 50)', clearly stating the verb (look up), resource (orders), and key constraint (up to 50 txids). This distinguishes it from sibling tools like query_trades (trades) or get_open_orders (open orders).

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 clear context: use this tool when you have specific transaction IDs to look up orders, with a limit of 50. It does not explicitly state when not to use it or name alternatives, but the context is sufficient for an agent to distinguish from siblings.

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