Get Rappi order invoice

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which the description redundantly restates with 'Read-only'. However, it adds the important behavioral detail that identity is redacted by default, which is not captured in structured data. This gives agents a key privacy-related expectation.

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?

Two short sentences with zero fluff. The core purpose and the default privacy behavior are presented first, and every word serves a purpose. It is appropriately sized for a simple retrieval tool.

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 (two enums), no output schema, and no parameter descriptions, the description is far too sparse. It does not explain what privacy_mode values do, what response_format affects, or what the returned invoice contains. Agents will struggle to call this correctly with only the given text.

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%, so the description must compensate by explaining the three parameters (order_id, privacy_mode, response_format). It does not mention any of them, leaving agents to infer from the schema enum names alone. This is a significant gap.

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 'Invoice for one order' clearly indicates the tool retrieves an invoice for a single order, which distinguishes it from siblings like get_order_receipt and get_order_status. However, it lacks an explicit verb like 'retrieve' or 'get', though the name itself implies the action.

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_receipt or get_order. There is no mention of prerequisites, exclusions, or context preferring this tool.

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