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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about freshness, source, rate limits, or what happens with an unknown postcode. It only enumerates data categories, which is descriptive rather than behavioral.

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?

One tight sentence with no filler, and the data categories are front-loaded. It is a fragment rather than a full statement, but nothing in it is wasted.

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 two-parameter read tool this covers the returned data categories reasonably well, including units (per sqm). However, with no annotations and no output schema, the absence of geography scope, currency, and freshness context leaves real gaps.

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%, so both parameters are already documented, giving a baseline of 3. The description does add value by enumerating the asset classes (retail, office, industrial), partially compensating for the enum-less property_type field, but gives no format or granularity detail for city_or_postcode.

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?

The description names the resource (commercial retail/office/industrial space data with NNN rates and vacancy) but is a bare noun phrase with no verb, so the action is only implied. It also does not distinguish itself from the sibling getRealEstateStats, leaving the agent to guess which one covers commercial property.

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?

There is no when-to-use guidance, no mention of geographic coverage limits, and no pointer to alternatives such as getRealEstateStats or getParcelZoningInfo. The agent must infer usage purely from the field list.

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