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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the per-type 200-id batching constraint; it says nothing about what 'full documents' contain or how paging behaves, leaving that to the schema.

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?

One compact sentence with the guidance front-loaded and the underlying endpoint appended as a trailing reference. No filler.

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 an 11-parameter read-only fetch with no output schema, the description establishes the id source, the per-type grouping and the batch cap. The only gap is a hint of what the returned 'full documents' look like, which a caller must infer.

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%, so every type array and the paging parameters are already documented. The description reinforces the 200-per-call cap and the 'per type' semantics, but adds little else beyond the schema.

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 concrete verb and resource ('Get full documents of one company by id, per type') and names the sibling that provides the ids. The 'full documents' vs id-list contrast implicitly separates it from saldeo_list_document_ids, but it never explicitly distinguishes it from saldeo_get_invoices_by_ids.

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?

Tells the agent where the ids come from ('use the groups from saldeo_list_document_ids') and gives a hard operational limit (at most 200 ids per call). It stops short of saying when to prefer this over saldeo_get_invoices_by_ids or saldeo_search_documents.

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