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 nothing behavioral beyond that – no ordering (newest first?), no truncation behavior at the 500 cap, no note that results are not filtered by customer or status. The 'SOAP GetInvoices_Recent' line is an implementation detail, not agent-relevant 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 fragments with zero padding, which is good, but the second sentence ('SOAP GetInvoices_Recent') consumes space without helping an agent decide or invoke. Brevity here reads as under-specification rather than discipline.

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 one-parameter, annotated, read-only list tool is a low-complexity case, and the schema covers the only argument. Still missing is the one thing 'recent' leaves ambiguous – whether results are newest-first and how this list is scoped versus kashflow_list_invoices.

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%; the count parameter already documents default 20 and max 500 in the schema. The description adds no meaning about count, so the baseline of 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?

The description names the resource and a qualifier ('most recently created sales invoices'), so the object is identifiable. But it is a noun phrase with no verb, and it never explains how 'recent' differs from the sibling kashflow_list_invoices or kashflow_list_customer_invoices, so an agent cannot reliably choose between them.

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?

There is no statement of when to use this tool, no prerequisites, and no reference to the many nearby siblings (kashflow_list_invoices, kashflow_list_overdue_invoices, kashflow_list_unpaid_invoices). The only cue is the word 'recent' in the name.

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