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

Goes well beyond readOnlyHint/idempotentHint: discloses that pool statistics may be SUPPRESSED for small pools, names the two flags to inspect (percentileSuppressed, suppressionReason), and warns never to present a suppressed statistic as a number. It also declares that every figure carries attributed series, period, sample size and vintage — exactly the behavioral context annotations cannot convey.

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?

Front-loads what it measures, then the suppression caveat, then the not-advice scope, then triggers. Dense and mostly earned, though the Hebrew trigger list and the parenthetical provenance detail make it longer than strictly necessary.

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?

No output schema exists, and the description compensates by describing the return shape at a high level (statistics plus provenance, per-track attribution) and naming two output fields. It still doesn't describe the full response structure, so an agent gets only a partial picture of what comes back.

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?

Only one parameter and schema description coverage is 100%, with the schema itself pointing to list_mortgages for the id. The description adds no further semantics about mortgageId, so the baseline of 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 precise verb+resource: statistical position of one mortgage's track rates against the Bank of Israel official average and the platform's consented pool. The scope (single mortgage, benchmark comparison, provenance-bearing statistics) is clear, but the description never names the sibling it differs from (get_boi_rates for raw series, compare_mortgages for mortgage-to-mortgage comparison), so an agent must infer the boundary.

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?

Gives a concrete use condition with verbatim user phrasings in Hebrew (האם הריביות טובות, השוואה לשוק, ריבית ממוצעת...) plus a scope exclusion: it does not say whether to sign, refinance or negotiate. That implicitly routes advisory questions elsewhere, though it doesn't name ask_advisor explicitly.

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