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

Annotations already state readOnlyHint/openWorldHint=false, so safety is covered. The description adds non-obvious behavior: only activated providers are returned, average rating is included, and radius mode switches output to include distance_km sorted ascending. No permission or pagination notes, but the added context is substantive.

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 with no filler; the result scope comes first, then the two query modes in priority order. Every clause carries information an agent needs.

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 carries the return shape (rating, distance_km, distance sort order) well. The only omission is max_results behavior, which is minor but leaves one parameter wholly undocumented.

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?

The description explains how near and radius_km interact and that results then carry distance_km sorted by distance, which is real semantic value. But max_results (one of four params) is undocumented in both the schema and the description, leaving a gap at 75% coverage.

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?

Names the resource precisely and adds a scope qualifier: only activated providers, returned with an average rating. No explicit verb ('search/list') and no differentiation from siblings such as provider_reviews or search_jobs, so an agent must infer the operation from the tool name.

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?

Explains the two operating modes (keyword/PLZ-prefix via q, vs. radius search via near + radius_km), which is useful invocation context. However it never states when to pick this tool over siblings or any prerequisites/limits beyond the radius bounds.

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