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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, covering the safety profile, so the bar is lower. The description nevertheless adds nothing beyond that: no return format, no pagination, no statement of whether the query object is required or what keys it accepts for a catalogue listing.

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 wasted words. It is efficient, though its brevity borders on under-specification for a tool with a free-form query parameter.

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 catalogue lister with annotations covering safety and no output schema, the basic scope is conveyed. But the ambiguous free-form query object and the lack of any hint about returned content leave gaps an agent would have to probe at runtime.

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% and there is a single optional parameter, so the baseline is 3. The description adds no meaning about the free-form 'query' object, whose arbitrary string/number/boolean properties would benefit from explanation of accepted filter keys.

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 (List) and resource (Finance Gate checks and data sources), so an agent knows this is a discovery/catalogue operation. However, it offers no differentiation from sibling catalogue tools (money_catalogue, tools_catalogue) or from finance_check, which it likely precedes.

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 explicit when-to-use guidance, no prerequisites, and no mention of the natural alternative (finance_check). The agent must infer that this is meant to be called first to discover available checks before running one.

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