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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the overdue/unpaid-in-full filter semantics and the fact that results are paged, but says nothing about ordering, return fields, or the SOAP call's cost/latency.

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?

Very short and front-loaded: the filter condition comes first, pagination second. The trailing 'SOAP GetInvoices_Overdue' is implementation trivia of marginal value but only costs a few words.

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 a simple read-only list tool with full schema coverage and annotations, the essentials are present. However, with no output schema and no statement of what an invoice record contains, the agent cannot anticipate the response shape or the ordering of results.

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 both parameters (limit, offset) are fully documented in the schema with defaults and bounds. The description adds nothing beyond schema, which is the expected baseline.

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 resource (sales invoices) with two concrete filter conditions (past due date, not paid in full) and notes it is paged. An agent can distinguish it from a general invoice list, though the distinction from the sibling kashflow_list_unpaid_invoices is left implicit.

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 filter definition implies when the tool applies, but there is no explicit 'use this instead of kashflow_list_unpaid_invoices when...' guidance, even though a near-duplicate sibling exists. Nothing states prerequisites or exclusions.

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