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

The readOnlyHint annotation already establishes safety, and the description adds useful behavioral context: filters combine with AND, pagination uses next_page as page, and the role id is the identifier used for booking and clinical notes. It does not describe authentication, rate limits, or response shape, but the annotation lowers the burden.

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?

The description is short and front-loads the core definition of a practitioner role before mentioning filtering, pagination, and the endpoint. The pagination sentence is slightly redundant with the schema, but overall it is efficient and easy to scan.

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?

With no output schema, the description provides enough context to invoke the tool correctly: it defines the resource, explains filtering semantics, and covers pagination. It could say more about what the returned records contain or how included related resources appear, but the essential invocation details are present.

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 all nine parameters are already documented in the input schema. The description adds only general filter behavior ('Filters combine with AND') and repeats the next_page-to-page pagination convention, which is already stated in the schema. Baseline 3 is appropriate.

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 gives a specific verb and resource: 'List or search practitioner roles,' and clarifies that a role is a practitioner's association with one clinic location. It is clear what the tool does, though it does not explicitly contrast itself with the sibling get_practitioner_role tool for single-record retrieval.

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 use case is implied by 'List or search' and by noting that filters combine with AND, but there is no explicit guidance on when to use this instead of get_practitioner_role or other list tools. The agent must infer the selection context from the tool name and sibling names.

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