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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds real value by naming the data sources consulted and explicitly bounding scope with "No claims about private ALM, intent or margins" – a useful limitation the annotations do not convey, though no output shape or granularity is described.

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?

Very short and front-loaded, with no padding. However, the opening sentence is a subject-less fragment that is harder to parse than it needs to be, which costs clarity relative to its brevity.

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 analysis tool with 8 parameters, 25% schema coverage, and no output schema, the description is thin – it neither explains what position data is returned nor how the cohort/loan/deposit parameters interact. The scope disclaimer helps, but an agent is left guessing at the tool's actual output and correct invocation.

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 only 25% (institutionId and depositKey), and 8 parameters exist, so the description must compensate. It names institutionId and gestures at a "product cohort," but leaves amount, payment, loanKey, loanKind, depositKind, and question entirely unexplained beyond their enums, so much of the surface is undocumented in both places.

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 fragment "Selected bank deposit and loan contracts against matching peer brands, own recorded history, RBA cash and dated funding disclosures" hints at a benchmarking/positioning operation but never states a clear verb+resource (list? compare? compute?). An agent cannot readily distinguish it from siblings like bank_analysis or compare_rates without opening the schema.

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 only says "Pass an institutionId and product cohort," which is parameter guidance, not when-to-use guidance. There is no mention of when to pick this over bank_analysis, compare_rates, or rate_details, and no prerequisites or exclusions are stated.

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