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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds that the check spans two distinct schemes with different deposit thresholds (5% vs 2%) and a location-dependent price cap, but says nothing about what the response contains or how ineligibility is reported.

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 naming the schemes first, then the qualifying distinctions, with no wasted clauses. It is dense but every phrase carries information.

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?

Annotations cover safety and idempotency, and no output schema exists. The gap is parameter meaning rather than missing behavioural framing, so for this complexity level the description is close to sufficient but still leaves key eligibility inputs undefined.

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 0% across 7 parameters, so the description must carry the semantic load. It hints at first_home, single_parent, price and state (via 'property price cap for the area'), but leaves location (capital vs regional, which directly drives the cap), will_live_in_it and all_buyers_citizens_or_pr entirely unexplained, which are the least self-evident inputs.

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 (Check eligibility) and a specific resource (Australian Government 5% Deposit Scheme / First Home Guarantee and Family Home Guarantee), including the price-cap dimension. No sibling tool in the list overlaps with eligibility checking, so an agent can route here 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 implies the scenario (a buyer considering a first-home or single-parent guarantee) but never states when to prefer this over assess_home_loan_readiness or calculate_stamp_duty, nor any exclusions or prerequisites. Usage is inferable from context only.

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