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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are limited to the API key's authorization scope, and it enumerates the returned entity fields. Pagination behavior is left to the schema rather than described.

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?

A single front-loaded sentence names the resource, its scope and its returned fields with zero filler. The trailing endpoint reference is compact and non-redundant enough not to detract.

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?

No output schema exists, but the description compensates by listing the returned fields, and annotations cover safety while the schema covers paging. An agent has enough to call it correctly; only pagination flow details are left implicit, which the schema already handles.

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%, with limit, cursor and offset each fully documented (defaults, max, paging semantics), so the schema carries the parameter burden. The description adds no parameter-level meaning beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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+resource ("List the practices") and adds the crucial scope qualifier "this API key can access," which no sibling shares. It also enumerates the fields returned, so an agent knows exactly what it gets. No other sibling tool lists practices, so it is unambiguous.

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 scope: fetch the practices available to the caller. There is no explicit when-to-use statement or routing to alternatives (e.g., elationhealth_list_physicians, which overlaps with the "physicians" field). No exclusions are given, so the agent must infer when this is the right call.

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