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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that paging happens 'here' and names the backing SOAP method GetReceiptsForSupplier, but says nothing about ordering, volume, or rate/permission constraints.

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 front-loaded sentence plus the SOAP method name; no filler. 'paged here' is slightly cryptic, but the concept is reinforced by the limit/offset parameters.

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?

No output schema exists, so the description carries some burden, but it conveys the record type (supplier invoices/receipts) and paging model, which is enough for correct invocation. It could have noted ordering or whether totals/summaries are included, a minor gap.

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; the description still adds value by emphasizing that supplier_id is numeric and pointing to kashflow_get_supplier as the source of that ID, which the schema does not say. Limit/offset semantics are left entirely to the schema, which is fine given its coverage.

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+resource+scope ('All purchases (supplier invoices / receipts) of one supplier') and pins the identifier to SupplierID, which distinguishes it from kashflow_get_receipt (single) and kashflow_list_recent_receipts (cross-supplier). An agent can select it without opening the schema.

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?

Explicitly tells the agent where the SupplierID comes from ('see kashflow_get_supplier') and that results are paged, giving clear preconditions. It does not explicitly state when to prefer kashflow_list_recent_receipts or kashflow_get_receipt instead, so it stops short of full alternative routing.

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