Fund Transactions

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact not in the annotations — that auth is required — but says nothing about pagination defaults, result ordering, or the default time window.

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 short sentences, front-loaded with the purpose and auth requirement before the filter list. Nothing is padded, though the trailing bare parameter enumeration is closer to a schema echo than prose.

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, all-optional-parameter listing tool with rich schema coverage and no output schema, the description covers purpose, auth and the available filters. Missing pagination defaults and result ordering are minor given the schema supplies defaults for start, category, currencies and business_type.

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 every one of the eight parameters including 'unix seconds' and the default-window behavior. The description merely restates the parameter names, adding no syntax or constraint detail beyond the schema; 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 clear verb and resource: 'List the user's fund cash-flow records,' which tells an agent exactly what data is returned. It does not, however, distinguish this from adjacent siblings like cash_flow, capital_flow, deposits, or withdrawals, whose names suggest overlapping territory.

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 description offers no when-to-use or when-not-to-use guidance and never names an alternative tool. 'Requires auth' is a prerequisite, not usage guidance, so an agent choosing among fund_orders, cash_flow and this tool gets no routing help.

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