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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a useful note that result groups vary by term, but its remark about returning display labels and search values largely duplicates what the existing output schema conveys.

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?

Two compact sentences with the core action front-loaded and the usage hint second. No filler, no redundancy.

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 one-parameter autocomplete with an output schema and read-only annotations, the description covers what the tool does, when to call it, and the nature of the input. Nothing essential is missing for correct invocation.

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?

There is a single parameter with 0% schema description coverage, so the description must carry meaning. 'from a free-text term' tells the agent the input is unstructured free text rather than an ID or enum, which is genuinely additive over the bare string 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?

States a specific verb and resource: 'Find Healthgrades provider, specialty, condition, or procedure suggestions from a free-text term.' It also positions itself relative to provider search. It stops short of distinguishing itself from other nearby siblings like healthgrades_top_searches or healthgrades_specialties.

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?

'use before provider search to resolve the query' gives a clear when-to-use and an ordering relative to a sibling tool. There is no explicit when-not guidance, but the sequencing instruction is actionable.

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