toast_get_order

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

No annotations are provided, and the description does not disclose behavior beyond the generic 'get' verb. It does not state whether the operation is read-only, what scope of order data is returned, or what happens when the GUID is invalid or not found.

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 front-loaded sentence with no filler. It communicates the core operation and key lookup mechanism in minimal words.

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 two-parameter lookup, the schema plus description is sufficient to invoke the tool. However, without an output schema, 'detailed information' is vague about the return contents, and no clarification is offered about what details are included.

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 already describes both parameters with 100% coverage, so the description does not need to add semantics. The schema documents orderGuid and restaurantGuid (including its default behavior), and the description adds nothing further.

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 states a clear verb ('Get'), a specific resource ('a specific order'), and the lookup key ('by GUID'). It is unambiguous but does not explicitly differentiate itself from siblings like toast_get_order_status or toast_get_orders_by_business_date.

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?

There is no guidance about when to choose this tool over toast_get_order_status, toast_list_orders, or toast_get_orders_by_business_date. The only implied usage is that a GUID is required, which is already visible in the input schema.

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