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

readOnlyHint=true already establishes a safe read, so the bar is lower; the description nonetheless discloses the paging envelope ('Returns a page plus next/previous'), which matters because there is no output schema. It stops short of auth or rate-limit notes, but adds real context beyond the 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 compact clauses with the resource and returned fields front-loaded, then the pagination behavior, then the endpoint. Zero filler or repetition.

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 two-parameter, zero-required list tool with no output schema, the description supplies the return fields and the next/previous paging contract, which is what an agent needs to page correctly. Nothing critical is missing, though filtering/sorting options are not mentioned.

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 coverage is 100% – page and page_size are fully documented in the schema with defaults and max. The description adds no syntax or ordering detail beyond the schema, so baseline 3 is appropriate even though it references paged results.

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 ('List the providers/doctors in the practice'), enumerates the returned fields, and cites the underlying endpoint GET /doctors. No sibling tool lists doctors, so the agent can place it unambiguously.

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?

Usage is implied by the name and the returned fields (browse practice providers), but the description never states when to reach for this tool versus, say, get_patient, nor any prerequisite. No exclusions or alternatives are named, leaving context to inference.

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