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

readOnlyHint and openWorldHint already cover the safety profile. The description adds real behavioral detail beyond the schema: fixed 20-per-page pagination, the cross-call dependency for filter codes, and the comma-separated convention for list filters. It stops short of noting rate limits or sort/interaction caveats.

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 sentences, with the core action and scope front-loaded before the return-fields list and the filter-source note. Dense but every clause carries information; slight over-packing of return fields that the output schema already covers.

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 16-parameter search tool with a companion filters tool, the description supplies the dependency and pagination model an agent needs. Since an output schema exists, the enumerated return fields are slightly redundant but not harmful, and nothing critical is missing.

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?

With 100% schema description coverage the baseline is 3, and the schema already documents values like age bands, distance, and availability enums. The description adds only the comma-separated list-filter convention and the provenance of filter codes, which is useful but marginal against a fully documented 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 (Search) and resource (Healthgrades physicians) plus the query axes (specialty, condition, procedure, name) and location scope (city or ZIP). An agent can distinguish it from single-entity siblings like healthgrades_physician and from the sibling facility search without opening a schema.

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?

It routes the agent to healthgrades_physicians_filters for insurance, plan, language, clinical-focus, and hospital filter values, keyed to the same query/where, which is a genuine when-to-use dependency. It does not, however, state exclusions or contrast against other Healthgrades search siblings.

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