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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds genuinely useful operational context absent from structured fields: pagination of 100 per page and the vendor rate limits (60 requests/minute, 1000 per 24 hours, one request per call). It stops short of describing return shape or ordering, but this is solid added value.

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?

Three dense sentences with no filler: scope first, then filters, then paging and rate limits. Every sentence carries new information and nothing is front-loaded poorly.

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 read-only, zero-required-parameter list tool with no output schema, the description covers scope, filtering surface, pagination and rate limits — enough to invoke it correctly. The only minor gap is that it does not hint at what fields a returned entry contains.

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 the schema already documents all nine parameters including enums and date formats. The description's filter summary (date, type, text, payment status) largely restates schema content without adding syntax or edge-case guidance, 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 general ledger entries) and enumerates the entry types it covers (manual entries, invoices, payments, VAT returns, depreciation), which distinguishes it from the narrower sibling lists such as smartaccounts_list_payments and smartaccounts_list_sales_invoices.

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 describes the available filter dimensions (date, type, text, payment status), which implies how to narrow results, but never states when to prefer this tool over the type-specific list siblings. Usage context is inferable rather than explicit.

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