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

Adds real behavioral context beyond the annotations: scope is limited to the homepage, results are not persisted, and the call is slow due to a page scrape — a useful latency warning no annotation conveys. The only tension is that readOnlyHint=false is conservative relative to 'Nothing is saved', but the description's disclosure is transparent and the mutation is correctly delegated to add_business_location.

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?

Three short sentences, front-loaded with the operation, then side-effect/routing, then the latency caveat. No sentence is redundant and none restates the tool name.

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?

With no output schema present, the description must carry the return contract and does so by listing the extracted fields, and it adds persistence, routing, and latency details an agent needs to sequence the call correctly. Nothing material is missing for this single-parameter tool.

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% for the single 'site' parameter, so the schema already documents it. The description adds the framing that the site is scraped via its homepage but no new parameter syntax or validation detail, which is the expected baseline when the schema carries the load.

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?

Specific verb+resource ('Reads the site's homepage') plus an explicit enumeration of what is returned (business name, address, phone, city). It is clearly distinguishable from siblings list_business_locations and add_business_location, which are named or implied by the routing instruction.

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?

Names the follow-up tool explicitly ('pass the result to add_business_location') and establishes the precondition that nothing is persisted, so the agent knows this is the detection step before a write. It stops short of stating when-not to use it (e.g., when a location already exists), so no exclusions are given.

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