Get FBO Order

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

No annotations are provided, so the description carries full burden. It states the tool returns details but does not disclose behavioral traits such as read-only nature, permissions required, rate limits, or any potential side effects. This is a significant gap for a retrieval 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 a single, well-structured sentence that front-loads the action and resource. It is concise yet informative. Minor improvement could be breaking into two sentences for better readability.

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 the tool has one parameter, no output schema, and no annotations, the description covers the key output aspects (products, quantities, prices, analytics, financial breakdown) adequately. It lacks prerequisites or error handling details but is sufficient for a simple retrieval tool.

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% with one parameter 'posting_number' that is well-described in the schema. The description adds value by specifying 'by posting number' and listing returned fields (products, quantities, etc.), but does not enhance parameter semantics beyond what the schema provides. 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 clearly states the action ('Get full details') and the resource ('single FBO order') with the required identifier ('by posting number'). It distinguishes itself from siblings (e.g., list_fbo_orders, get_fbs_order) by specifically mentioning 'FBO order' and 'posting number'.

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 provides clear context (what the tool does and how to use it) but lacks explicit guidance on when to use this tool versus alternatives (e.g., list_fbo_orders for multiple orders, get_fbs_order for FBS orders). No exclusions or when-not scenarios are mentioned.

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