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

readOnlyHint=true already establishes a safe read, so the bar is lower. The description adds useful analysis context (floor-area jumps as red flags), but does not disclose pagination, ordering of certificates, or coverage limitations (e.g. only lodged EPCs).

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?

Two tight sentences: the first front-loads what is returned, the second frames why it matters. No waste, though the red-flag sentence is advisory rather than strictly definitional.

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 single-parameter read-only history tool with no output schema, the description covers what is returned and one important interpretation. Minor gaps remain around ordering, pagination, and empty-history behavior, but nothing essential to invoking it is missing.

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% and the property_id parameter already documents that it is an EPC lmk-key returned by search_property. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 3 is correct.

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+resource: retrieving all EPC certificates for a property over time, and enumerates the per-certificate payload (floor area, room counts, rating). Clearly distinct from sibling check_epc_compliance (compliance status) and get_planning_history (planning records).

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?

Implied context of a transaction/due-diligence workflow is present via the cash-buyer framing, but there is no explicit when-to-use versus check_epc_compliance or when the data is unavailable. No exclusions or alternatives named.

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