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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds that results are "verified" listings plus "top companies", but says nothing about result volume, ordering, pagination, or coverage limits for a given city.

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 with no filler; the resource type and geo scope come first. It could append one routing clause without bloat, but as written nothing 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 one-parameter read-only tool with no output schema, the description conveys roughly what comes back (listings, companies). It still leaves unclear how this differs from search_listings and whether results are bounded, which an agent needs to choose correctly.

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 single parameter is documented as a lowercase hyphenated slug, so the schema carries parameter meaning. The description's examples ("Leeds or Manchester") are capitalized, which mildly conflicts with the schema's lowercase-slug requirement rather than adding correct guidance.

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 a concrete verb ("Find") and concrete resources ("verified home and interiors listings and top companies"), scoped to a UK city, so an agent can tell what it returns. It never differentiates itself from siblings like search_listings or listing_detail, which is the missing piece for 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?

There is no statement of when to use this instead of search_listings, listing_detail, or company_check, and no exclusions or prerequisites. The only usage signal is implicit: give it a UK city name.

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