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

The description goes well beyond the readOnly/openWorld annotations: it explains that robots.txt is checked first and closed sites are not read, that the home page, sitemap, and up to 25 location pages are crawled, what the eight checks are, how the score is derived, and that it cannot confirm whether a business is really at an address. This is rich behavioral and return-context disclosure for a read-only audit tool.

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?

The purpose is front-loaded, but the description is a single dense run-on sentence that packs in every check and caveat. It is hard to scan, and phrases like 'state and city listings followed down to the places and subpages every location has left out' reduce clarity rather than earning their place.

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 complex multi-location audit tool with no output schema, the description is complete enough: it covers crawl scope, the 25-location limit, all eight checks, how failures and fixes are reported, the score, and the key limitation. An agent can understand what it will get back and what the tool cannot do.

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 url parameter already documents the expected site format with an example. The description adds only the broad idea that the URL is the brand's site being graded, not extra format, edge-case, or validation semantics 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?

The description states a specific action: it grades a brand's location pages as a free multi-location grader, with eight checks and a 0-100 score. That is clearer than a generic listing tool, but it does not reconcile the 'List' title/name with the actual grading behavior, nor does it differentiate this tool from siblings like mttr_pages, mttr_site, or mttr_reviews.

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?

It indicates this is the free multi-location grader, implying it is for auditing location pages, but it gives no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives among the many sibling tools. The caveat that it cannot verify physical presence is useful but is not usage routing.

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