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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real behavioral detail beyond that: a batch cap of 50, the acceptance of ids or postcodes, MEES 2030 as the comparison threshold, and that expired certificates are flagged. It stops short of describing result shape or failure handling for large/invalid batches.

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, front-loaded with the operation and its constraints, ending with the usage case. No filler or redundancy.

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 one-parameter read-only tool with no output schema, the description covers operation, input forms, batch limit, threshold standard, and the notable output signal (expired-certificate flags), and it names the target user scenario. Only the exact result fields and behavior on oversized/invalid batches remain unstated.

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 100% and the single parameter already documents 'Property ids and/or postcodes, up to 50.' The description restates the same constraint (batch, id-or-postcode) without adding syntax, formatting, or mixed-input rules beyond the schema.

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 (batch-check properties against MEES 2030 thresholds) and adds concrete behavior (flagging expired certificates). It is clearly distinct from domain siblings like get_epc_history in spirit, but it never explicitly says how it differs from the EPC-history or property-summary tools.

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 closing sentence gives an explicit usage context: 'Use for landlord portfolio compliance sweeps.' This tells the agent the intended scenario (portfolio-level batch compliance), but it does not name alternatives or state when a single-property tool would be better.

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