get_order

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

The readOnlyHint annotation already signals that this is a safe read operation. The description adds the return payload structure, which is useful but not strictly behavioral beyond the annotation. It does not disclose error conditions or side effects, but for a simple get operation this is acceptable. 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 concise and front-loaded with the purpose, then provides a structured example of the return object. The additional field listing is useful but slightly redundant given the output schema, yet it does not feel overly 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?

The tool is simple with one parameter, high schema coverage, and an output schema. The description covers the return format and key fields, providing enough context for an agent to use it correctly. It could mention not-found behavior, but that is not essential given the schema and annotations.

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 100%, and the schema already thoroughly explains the order_specifier parameter, including examples of Oanda-assigned IDs and client-assigned IDs with '@' prefix. The description repeats this information without adding substantial new parameter context, so 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 starts with 'Get a single order by ID or client-assigned ID.' This uses a specific verb ('Get') and resource ('single order'), and clearly differentiates from sibling tools like list_orders by emphasizing the singular retrieval and supporting client-assigned IDs.

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 retrieving one specific order, but does not explicitly mention alternatives or when not to use it. Context makes it clear that it is for single-order retrieval, which provides clear guidance without exclusions.

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