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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description adds material behavioral detail: scores equally weight eligible source ratings on a 10-point scale and use an approximate academic conversion for BBB grades. This helps the agent interpret results and is not available from the schema or annotations.

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 sentences with no fluff: the first front-loads purpose and filters, the second adds scoring methodology, and the third routes to an alternative. Every sentence earns its 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?

The description covers purpose, filters, sort, scoring behavior, and an alternative. It does not mention pagination (offset/limit) or inclusive/exclusive boundary semantics for the score range, but the output schema exists and the input schema provides defaults/max, so an agent can still proceed confidently.

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 0%, so the description must compensate. It maps query, Review Score range (minScore/maxScore), rating availability, and sort options (alphabetical/by score). It does not explain limit/offset, but those are standard pagination parameters and the schema already provides defaults and bounds.

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 begins with a specific verb and resource ('Search published provider reviews') and clearly names the filtering dimensions (query, Review Score range, rating availability) and sort options. It also distinguishes itself from the sibling get_provider_reviews by pointing to source-level evidence, so an agent can tell them apart.

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?

The description explicitly says 'Use get_provider_reviews for source-level evidence', giving a clear when-not and an alternative. The main use case is implied by the filter and sort semantics, so the agent knows when to invoke this tool versus the named sibling.

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