get_invoice

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

No annotations are provided, so the description carries the full burden. It discloses that the result includes full detail and lines, which is useful, but it does not explicitly mention read-only behavior, error handling, or authentication requirements. For a simple getter, the description provides basic but not rich behavioral context.

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 one concise sentence, immediately states the main purpose, and contains no unnecessary filler. It is optimally front-loaded and every word contributes value.

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 no annotations, no output schema, and no parameter coverage, the description is too sparse for a complete tool understanding. It does not specify return fields beyond 'lines', does not clarify how to obtain the move_id, and gives no error or prerequisite context. The simple structure does not fully compensate for these gaps.

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 the move_id parameter or its relationship to the invoice/bill. The schema only shows an integer ID titled 'Move Id', which may be ambiguous for agents unfamiliar with Odoo's account.move model. The description fails to compensate for the lack of parameter documentation.

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 tool provides full detail of a single invoice/bill including lines, which is a specific retrieval operation. It distinguishes from siblings like search_invoices by emphasizing 'one invoice' and 'including its lines', effectively communicating scope and resource.

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 use when full detail of one invoice is needed, but it does not explicitly state when to use this tool versus search_invoices or other siblings. There are no clear exclusions or alternative recommendations, so usage context is only implied.

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