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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context: it is scoped to a single division and requires the user's Cotlet API key with app access, which the annotations do not convey. It stops short of stating pagination semantics despite a cursor-based schema.

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?

The opening sentence and the post-colon clause restate the same field list ('customer, amount, due date and status') almost verbatim, wasting space. The auth note is useful but the repetition dilutes front-loading.

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?

There is no output schema, so the description carries the burden of describing return values and does so (customer, amount, due date, status with example values). Combined with the safety annotations and fully documented schema, it is nearly complete for a read-only list tool.

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%, so all five parameters are already documented. The description reinforces status ('such as Open or Processed'), the due-date filter goal and division scoping, but adds no syntax or format detail beyond the schema, so the 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 outstanding receivables') plus the exact content returned (customer, amount, due date, status) and the scope (one division). An agent can distinguish it from exact-online_list_sales_invoices without opening either 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?

It hints at a use case ('Filter by status or due date to find what is overdue') and states the auth requirement, but gives no explicit when-to-use vs when-not guidance or named alternatives. Usage is implied rather than directive.

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