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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so the safety profile is covered. The description adds meaningful context beyond that: it requires an authenticated RealYield account, can take up to 30 seconds, returns a 0-100 score with parts/flags/summary/report link, and results are educational estimates rather than advice.

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 the purpose and then covers coverage, return format, caveats and prerequisites. The long enumerations of checked data are dense but earn their place since no output schema exists to describe the report contents; only slight trimming would help.

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?

With no output schema, the description fully carries the burden: it names the geographic scope, the returned score components, flags and report link, plus authentication, latency and the educational-estimate disclaimer. An agent has everything needed to call and interpret this tool.

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 coverage is 100% across all 16 parameters, so the baseline is 3. The description reinforces that rent defaults to the ONS area average and that the postcode is the property's rather than the user's location, but these points largely restate what the schema already documents, so it adds only marginal meaning.

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 with clear scope: it checks a specific buy-to-let property in England or Wales using live public data. An agent immediately knows what the tool produces. It does not explicitly distinguish itself from the sibling analyse_buy_to_let_deal, so it falls short of 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 context is implied (a full deal check on a specific property given its address and characteristics) and it discloses prerequisites (RealYield sign-in) and cost (up to 30 seconds). However, it never says when to prefer this over analyse_buy_to_let_deal or the narrower calculators in the sibling set, leaving routing to inference.

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