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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the returned-field inventory and the conditional geo-search behavior, but says nothing about pagination/response shape beyond what the schema documents.

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 tight sentences, front-loaded with the operation and returned fields, with the optional search and endpoint appended. No filler, though the field enumeration is on the dense side.

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?

There is no output schema, so the field list in the description usefully tells the agent what comes back, and the annotations plus schema cover safety and pagination. Complete enough to call correctly, though it could mention the default sort or result shape.

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 100%, so limit, offset, distance, and near_zip are already fully documented in the schema. The description only gestures at the postal-code search, adding no syntax, defaults, or constraints beyond the structured fields, so baseline 3 applies.

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 (List) and resource (practitioners), enumerates the salient fields returned (bio, NPI, specialties, panel size, enrollment settings, locations), and gives the underlying endpoint. It is clearly distinguishable from the singular sibling get_practitioner.

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 notes the optional proximity search (near_zip/distance) but gives no explicit guidance on when to use this list tool versus get_practitioner or list_locations, nor any exclusions. Usage is implied by the verb rather than stated.

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