Get iFood order

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

Annotations already convey read-only, idempotent, and non-destructive behavior. The description adds only the v3 version marker and the scope constraint 'one order by id'. It does not clarify privacy_mode behaviors or response formatting, but the core safety profile is covered by annotations.

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 very concise and front-loaded, with the core purpose in the first phrase. However, 'Read-only' duplicates the readOnlyHint annotation, which is redundant within the description, though it remains efficiently structured.

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?

With three parameters, no output schema, and no parameter-level documentation, the description is incomplete. It omits guidance on privacy_mode semantics and does not contrast itself with ifood_list_orders, so an agent would need to infer important invocation details.

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 description coverage is 0% and the description does not explain privacy_mode or response_format. Only 'by id' hints at order_id. An agent gets no guidance on choosing between summary, structured, or raw, or when to prefer markdown over json.

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 it retrieves one order by ID and notes the API version (v3). This distinguishes it from the sibling tool ifood_list_orders, which handles multiple orders. The read-only nature is also highlighted.

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 phrase 'One order by id' implies the tool should be used when a single order is needed and an order_id is available. However, it does not explicitly name alternatives or state when not to use it, leaving the decision to inference.

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