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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true). Beyond that, the description adds genuinely new behavioral context: that the result is paged and that the reply carries 'total' and 'next_offset', which tells the agent how to iterate — important since no output schema exists.

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 compact sentence that front-loads the resource and its fields, then the paging behavior. Very little waste, though the SOAP method reference ('SOAP GetCustomers') is filler for an agent that only needs MCP semantics.

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 two-parameter, no-required-args list tool, the description covers what is returned, which fields appear, and how pagination is surfaced — filling the gap left by the absence of an output schema. Missing only explicit routing guidance against the many sibling lookup tools.

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%, with both limit and offset fully documented including defaults and maximums, so the baseline is 3. The description nods to paging ('next_offset') but adds no format or semantics beyond what the schema already states.

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 states a specific verb and resource ('All customers') and enumerates the fields returned, so the agent immediately knows this is an unfiltered customer dump. It does not explicitly differentiate from siblings like kashflow_get_customer_by_id or kashflow_find_customer_by_email, though 'All customers' plus paging implies the distinction.

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?

Usage is only implied: 'All customers' suggests this is the bulk-list path rather than a lookup, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative such as find_customer_by_email. An agent must infer the routing decision itself.

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