Get external sales invoice

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds one piece of behavioral context: the response includes lines and payments. This is useful but does not cover auth, error, or response-shape details; there is no contradiction with 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?

A single sentence with no filler. The core action, resource scope, and included content are front-loaded and every word earns its place.

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 low-complexity read-only retrieval with strong annotations, the description is nearly sufficient: it names the resource and key included content (lines, payments). The only meaningful omission is richer return/error context, but no output schema exists to fill that gap and the tool is simple enough that this is a minor deficiency.

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 coverage is 50%; external_sales_invoice_id has no schema description and the tool description does not clarify it beyond its self-explanatory name. administration_id is already described in the schema, so the description contributes no additional parameter meaning.

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 specific verb and resource: 'Retrieve one external sales invoice, including its lines and payments.' It clearly differentiates from siblings like list_external_sales_invoices (by 'one') and get_sales_invoice (by 'external').

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 choose this tool over list_external_sales_invoices or alternative lookup tools like find_sales_invoice_by_invoice_id. The singular 'one' weakly implies a direct-id lookup, but no explicit when/when-not or alternative routing exists.

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