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

Annotations already declare readOnly=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds that results are scoped to the newest records (not a full listing), but says nothing about sort order or how 'recent' is bounded beyond the schema's count parameter. 'SOAP GetReceipts_Recent' is implementation detail rather than behavioral context.

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 short sentences, front-loaded with the resource and scope. The trailing 'SOAP GetReceipts_Recent' is low-value internal plumbing that consumes space without helping an agent decide or invoke.

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?

A simple read-only list with annotations covering safety, a fully documented single parameter, and no output schema, so the description is close to sufficient. What's missing is how this differs from kashflow_list_supplier_receipts and kashflow_get_receipt, which matters given the dense receipt/invoice sibling set.

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% and the single 'count' parameter is fully documented in-schema with default (20) and maximum (500). The description adds no syntax or semantics beyond that, so baseline 3 applies.

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 (list the most recently created purchases / supplier invoices / receipts), with the parenthetical clarifying terminology. It implicitly separates itself from kashflow_list_supplier_receipts and kashflow_get_receipt via the 'most recently created' qualifier, but never names those siblings, so the differentiation is left to inference.

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?

'The most recently created' implies the scenario (surveying newest activity) but there is no explicit when-to-use, no exclusion, and no pointer to kashflow_list_supplier_receipts for full/filtered retrieval. Usage is only implied.

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