get_open_orders

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

With no annotations, the description must carry the behavioral disclosure burden. It discloses one behavior (filtering by symbol), but does not mention auth requirements, pagination, return format, or behavior when no symbol is passed. This is minimal context for a trading tool.

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 extremely concise, consisting of two short sentences. It front-loads the main concept ('Ordenes abiertas') and immediately follows with the filter condition. No redundant words, though the first sentence is a fragment rather than a complete statement.

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?

For a simple tool with one optional parameter and no output schema, the description is adequate but not complete. It explains the symbol filter but does not state what the return value is, whether it returns all orders for the account, or any limitations. Given the low complexity, it hits the minimum threshold.

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 zero description coverage for the symbol parameter, and the description compensates by explaining its effect: 'Si pasas symbol, filtra por ese par.' This provides clear semantics for the only parameter, though it leaves format specifics to 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 'Ordenes abiertas' is a noun phrase that essentially restates the tool name (get_open_orders), lacking an explicit verb like 'lists' or 'returns.' It does clarify the resource and adds a filter condition, but the core action is implied rather than stated, making it vague.

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?

No guidance is provided about when to use this tool versus alternatives. The description only mentions an optional symbol filter and does not reference sibling tools such as get_my_trades or get_account, nor does it explain use cases or exclusions.

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