get_order_finances

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

With no annotations, the description must convey behavioral traits. It indicates a read operation (financial breakdown) but omits any details about required permissions, rate limits, idempotency, or potential side effects. The agent has no information about the tool's safety or side effects beyond the implied read nature.

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 a single short sentence, which is concise. However, it sacrifices completeness for brevity. It adequately front-loads the purpose but fails to include essential details about parameters and usage.

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 an output schema exists, the description could afford to be less detailed about return values, but it still needs to explain the tool's behavior and parameters. The description is inadequate for the tool's complexity (2 parameters, financial context) and does not provide enough context for an agent to use it confidently.

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 schema has 0% description coverage for parameters, yet the description provides no clarification. The order_id parameter is required but not explained (e.g., format or source), and the marketplace parameter's optional nature and purpose are completely absent. The agent must infer meaning solely from parameter names.

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 the tool provides a financial breakdown of an order, listing fees, net, and margin. It indicates the specific resource (order finances) and distinguishes itself from general order retrieval or sibling tools like get_order_items by focusing on financial data.

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 on when to use this tool versus alternatives such as get_order_metrics or estimate_fees. There is no mention of prerequisites, ordering of calls, or any other context that would help an agent decide to invoke this tool.

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