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

Annotations already cover read-only and closed-world, so the description earns credit for disclosing return fields (phone, website, licence, listing page), ranking order, absence of paid placement, and owner-affiliation disclosure. It omits any pagination behavior even though a 'page' parameter exists.

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 tight sentences, front-loaded with the action and inputs before the return/shape details. No filler, though the opening slightly repeats the tool title.

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, the description usefully names what comes back and the integrity/disclosure context. The main gap is pagination, which matters for a tool with a 'page' parameter and no required inputs.

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 60%, so the schema carries most of the load. The description restates query/city/state in prose but adds nothing on the 'page' parameter's semantics or on combining query vs. category filters.

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 ('Search the DouxProcess Directory for businesses') plus the intended lookup axes (need, city, state). Clear that this is a multi-result search versus the sibling get_business, though the distinction is inferred rather than stated.

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?

Usage is implied by the examples ('roofer, dentist, insurance agency'), but there is no explicit when-to-use, when-not-to-use, or routing to get_business or list_categories. The category-to-list_categories link lives only in the schema, not the description.

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