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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the 200-id cap and the underlying POST endpoint, plus that full (not partial) invoice objects come back. It says nothing about behavior for ids that don't exist or belong to another company, which is the main unknown for a batch-by-id fetch.

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 compact sentences, front-loaded with the verb and scope, followed by the id source and the batch cap. The trailing endpoint reference is the only arguable overhead and is short enough not to hurt.

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 7-parameter read-only fetch with full schema coverage and no output schema, the description covers scope, id provenance, and batching. It could go further by sketching the returned invoice structure or confirming paging behavior of the reply, but nothing critical 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?

Schema description coverage is 100%, with per-parameter descriptions for invoices, pre_invoices, corrective variants, limit and offset, so the schema does the heavy lifting. The description only reinforces the id source and the 200-item ceiling already encoded as maxItems, adding no new 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?

States a specific verb and resource ('Get full invoices'), the scope ('of one company'), and the id source, which separates it from the sibling saldeo_list_invoice_ids that only returns ids. It does not explicitly distinguish itself from saldeo_list_invoices, so the boundary with that sibling is left implicit.

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?

It gives a prerequisite chain ('ids from saldeo_list_invoice_ids') and a hard batching constraint ('at most 200 per call'), which is useful operational context. However, there is no statement of when to prefer this over saldeo_list_invoices or what to do when a batch exceeds 200.

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