orbs_query_orders

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

Annotations already indicate readOnlyHint and openWorldHint, so the safety profile is clear. The description adds value by disclosing the fallback to SDK query if the API is unavailable – a behavioral detail not captured in annotations. No contradiction detected.

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 only two sentences, front-loaded with the core purpose. Every word contributes meaning, and there is no redundancy or filler.

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?

The tool is a straightforward read-only query with well-documented parameters and no output schema. The description covers the purpose, filters, and fallback. However, it does not describe the return format or any pagination, which would be useful since there's no output schema. Still, for a simple query tool with readOnlyHint, it's mostly complete.

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 100%, with each parameter (hash, chainId, swapper) having its own description. The tool description merely restates the swapper and hash filters without adding extra meaning or clarifying chainId's default behavior beyond the schema. Baseline 3 is appropriate.

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 'Query Spot orders by swapper address or order hash' – a specific verb (Query) + resource (Spot orders) with explicit filter criteria. It distinguishes itself from sibling order tools like orbs_cancel_order or orbs_place_order by being a read-only lookup tool.

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 implies usage for querying existing orders and adds a fallback behavior ('Falls back to SDK query if Spot API unavailable'), which helps agents decide when to rely on it. However, it doesn't explicitly exclude alternatives or state when to prefer this over other order tools, so it falls short of a 5.

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