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. The description adds one behavioral nugget -- that results include document-matching status -- but says nothing about pagination, ordering, or default scoping (e.g. companyId required to get meaningful data).

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 front-loaded sentence with no filler, which is structurally sound. However it is arguably too terse for a 3-parameter list tool that is missing usage and parameter guidance.

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 should hint at return contents; it does mention matching status, which is useful, but omits pagination/limit behavior and the meaning of unrelated parameters. Annotations carry the safety burden, keeping this at a minimum-viable level.

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 coverage is only 67% (companyId has no description at all), and the description contributes nothing about limit, matched, or companyId. It does not compensate for the undocumented parameter or clarify default behavior beyond what the schema already states (min/max, default 50, enum meaning).

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 names a specific resource (bank transactions) and adds scope ('stazene' = downloaded) plus the matching-status facet. No sibling tool covers transactions, so no differentiation is strictly needed, but it does not explicitly contrast with list_documents or search.

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 no indication of when to call this versus siblings such as search, list_documents, or get_cashflow, nor any prerequisite or context conditions. The agent must infer usage entirely from the name.

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