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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description contributes beyond that by naming the returned field set (id, name, parent, level, financial account) — valuable because there is no output schema — and by citing GET /api/v6.1/funds. It omits pagination behavior and any rate-limit or ordering notes, keeping it below a 5.

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?

One sentence plus an endpoint reference, zero padding, and the disambiguating gloss on 'funds' is front-loaded where it matters most. Nothing is wasted.

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 six-parameter read tool with a complex filters object, the rich schema carries parameter semantics and the annotations carry the safety profile; the description fills the gap left by the absent output schema by listing returned fields. What remains unmentioned — pagination across offset/limit, default ordering behavior, response envelope — is minor and partly recoverable from the schema.

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%, with sort, limit, fields, offset, direction and the nested filters object each documented in the schema including operator syntax and examples. The description adds nothing about parameters, so the baseline 3 applies — the schema does all the work here.

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 the cash/bank funds') and immediately disambiguates what a 'fund' is with the parenthetical 'accounts for receipts and payments', which matters because a sibling named getfly_list_accounts exists. It also enumerates the identifying fields returned and cites the exact endpoint. It stops short of explicitly contrasting itself with that sibling by name, so a 4 rather than 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?

Usage is only implied: an agent can infer this is the read path for the funds resource, and the parenthetical hints it is the right choice when receipts/payments accounts are needed. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. vs getfly_list_accounts), which leaves routing to inference.

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