Get Open Orders

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no behavioral context beyond these hints—it does not explain what 'working orders' means, whether it reflects live broker state, or any rate limits/pagination. It is a minimal restatement of the title.

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 short ('Working orders on the configured broker account'), making it concise. However, it is under-specifying and reads as a sentence fragment rather than a complete, informative statement. It is not as well-structured as descriptions that use a full sentence.

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?

This is a very simple tool with no parameters and no output schema, but the description is still incomplete. It does not state return format, whether results are sorted, what statuses qualify, or any caveats. The sibling tool 'get_open_positions' suggests a potential confusion point, and the description does not address it.

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?

There are no parameters, so the schema provides full coverage. The description does not need to explain parameters. A baseline of 4 is appropriate given the zero-parameter structure.

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 title 'Get Open Orders' combined with the description 'Working orders on the configured broker account' clearly indicates the tool retrieves open/working orders. The resource is specific and distinct from siblings like 'get_open_positions' or 'draft_order', though the description itself lacks an explicit verb.

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 on when to use this tool versus alternatives. The description is merely a noun phrase and does not mention prerequisites, context, or exclusions. It relies entirely on the tool name for usage context.

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