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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description adds real behavioral detail: unfilled recognition fields come back as null, and the call requires the user's Cotlet API key with app access. Pagination behavior is left to the cursor param in 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?

The core scope statement is front-loaded, which is good, but the opening two sentences restate the same idea twice ('fields the automatic recognition filled in' / 'as the automatic recognition read them'), and the field list is duplicated in prose. Roughly a quarter of the text is redundant.

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 output schema, the description carries the return-value burden and largely does: it names the fields surfaced (status, contact, receipt number, date, amount) and explains the null case. Auth requirements are stated. Only pagination shape and ordering are absent, which the schema's cursor param partly implies.

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 100% so the baseline is 3, but the description goes further for the most consequential parameter by explaining what status=to_check actually means (receipts awaiting 'Beleg erfassen'), which the terse schema enum text does not convey. limit, cursor and from_date still rely entirely on 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?

The description gives a concrete verb ('Lists') plus the resource ('uploaded receipts') and enumerates the returned fields, so an agent knows exactly what it retrieves. It is distinguishable from sibling list tools by the 'receipts' resource, but it never explicitly contrasts itself with lexware-office_list_documents, which is the nearest ambiguity.

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 one actionable routing hint: use status=to_check for receipts still awaiting 'Beleg erfassen'. That is genuine usage guidance for a parameter value, but there is no when-to-use/when-not-to-use statement, no mention of when list_documents or a receipt lookup would be the better call.

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