open_orders

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

No annotations are provided, and the description only notes that authentication is required. It does not disclose any behavioral traits such as pagination, rate limits, or how open orders are defined. The description carries the full burden but adds minimal value beyond stating the operation.

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 very short (one sentence with a tag), which is concise and front-loaded. However, it lacks structure and could benefit from additional context without becoming verbose.

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 that the tool has a single optional parameter, no output schema, and no annotations, the description is incomplete. It does not explain what data is returned (e.g., order details), ordering, or limitations. For an agent to correctly use this tool, more context is needed.

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 100% coverage for the single parameter 'pair', which includes a description. The tool description adds no additional semantic meaning beyond what the schema already provides. Thus, baseline score of 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 'List open orders', specifying the verb and resource. While it is not explicitly differentiated from siblings like 'order_history' (which lists all orders), the context of sibling names provides some implied distinction.

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 includes '[REQUIRES AUTH]' but offers no guidance on when to use this tool versus alternatives (e.g., 'order_history' or 'get_order'). There is no mention of prerequisites or context for use.

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