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 elsewhere. The description confirms the tool reads open (unpaid) items only, which is meaningful scope, but says nothing about pagination behavior, result size limits or how 'open' is determined (e.g. partial payments).

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, the core resource is front-loaded and the field inventory follows in a compact list. Nothing redundant, and the trailing API constant names cost little.

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?

With seven optional parameters and no output schema, listing the returned fields (date, contact, open and original amount, reference, due date) usefully compensates for the missing return spec. The remaining gap is that paging and administration scoping are left entirely to the schema descriptions.

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 limit, offset, sort_order, the date range and include_bank_transactions are all self-documented. The description only restates the optional date range and the returned field list, adding no semantics 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+resource: 'Open items on the debtors list (unpaid sales invoices)', and enumerates which fields come back. The debtor/creditor split implicitly separates it from yuki_list_outstanding_creditor_items, but that alternative is never named.

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?

Only 'Optionally within a date range' hints at usage. There is no statement of when to pick this over yuki_list_outstanding_creditor_items or yuki_list_gl_account_transactions, and no prerequisites such as needing an administration_id when the key spans multiple administrations.

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