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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds real context beyond that: results are paginated and each carries an acDocumentId usable with add-transaction-comment, which tells the agent how the output is consumed. It omits ordering, result caps and empty-result behavior.

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, zero padding, and the core action plus its key output contract are front-loaded. Every clause earns its place.

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 no output schema, the description usefully states that returns include acDocumentId, and the schema covers all input details including pagination defaults. It is nearly complete; a note on result ordering or the total result set would close the remaining gap.

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 page, perPage, dateFrom, dateTo and companyId are already fully documented in the schema. The description only adds 'with pagination', which is redundant with the schema's page/perPage entries, 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?

The description gives a specific verb+resource ('Search transactions for a company') and adds the pagination scope, which is more than the bare name. However, it does not distinguish this tool from the sibling search-accounting-transactions, so an agent must infer the difference.

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?

There is a useful downstream hint that the returned acDocumentId feeds add-transaction-comment, which implies a chaining workflow. But there is no explicit when-to-use vs. when-to-use-an-alternative guidance, and the near-identical sibling search-accounting-transactions is never addressed.

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