Get a Toast order summary

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

Although the annotations already indicate read-only, idempotent, and non-destructive behavior, the description adds meaningful transparency by explicitly stating that customer identity, contact, delivery, and payment-card fields are excluded from the response. This clarifies the scope of returned data beyond the annotation flags.

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 sentence that concisely conveys the primary action and the key exclusion. There is no redundant or extraneous information, making it well-structured and easy to parse.

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 get-by-ID operation, the description covers what it does and what it returns (with exclusions). Since the tool has an output schema, the description does not need to explain return values, and no other critical context is missing.

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?

Both parameters are fully described in the schema (orderGuid as 'Toast order GUID' and restaurantGuid with default behavior), giving 100% coverage. The description text itself does not add additional meaning to the parameters beyond referencing the GUID in the action, so it remains at the baseline for schema coverage.

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 (gets one order), the resource (order), and the identifier (Toast GUID). It also distinguishes itself from sibling tools like find_orders by indicating it retrieves a single order by GUID rather than searching.

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 when to use this tool: when you have a specific Toast order GUID and need a single order. It also implicitly warns against use when customer identity, contact, delivery, or payment-card fields are needed, as these are excluded. However, it does not explicitly name alternative tools like find_orders for search scenarios, so it falls slightly short of full explicit guidance.

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