Get the transactions of a conversion

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered and the description only needs to add context. It adds the shape of the data returned (date, description, signed amount, balance, account, period), but says nothing about pagination, result limits, or what happens if the conversion id is unknown. Adequate given the annotation coverage, but not rich.

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: verb, resource, scope, and payload, with no filler. The field enumeration earns its place because there is no output schema, though the trailing 'with the account and period' is slightly tacked on.

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 compensates by naming the returned fields, and annotations cover the read-only safety profile, so an agent can call it correctly. It is thin on error behavior and pagination for a potentially large transaction list, but nothing essential is missing for the core call.

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 baseline is 3; the description covers the required conversion_id implicitly and mentions the account/period framing. The advanced 'tables' page:table parameter is documented only in the schema, and the description adds no syntax or defaulting detail beyond it. 0 params semantics fine.

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 ('Get the transactions of an earlier BankConv conversion') and even enumerates the returned fields, so the agent knows this is the per-conversion ledger read rather than the credits or statement list. It never names a sibling (list_conversions, download_statement, get_credits) to disambiguate, so it stops short of a 5.

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?

The phrase 'an earlier BankConv conversion' implies the prerequisite that a conversion already exists, which is useful but only implied. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as download_statement or list_conversions.

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