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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the underlying endpoint (GET /physicians/) and the returned field set, which is modest extra context but says nothing about auth requirements, rate limits, or paging behavior beyond what the schema states.

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 compact sentence with the resource up front, followed by a short endpoint reference. The dense field enumeration earns its place in the absence of an output schema; nothing is padded.

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 usefully enumerates the returned fields, and paging is thoroughly specified in the input schema. For a read-only list endpoint with full annotation coverage, what remains unsaid is minor.

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 every parameter (npi, limit, cursor, offset, last_name, first_name) is already documented in the schema, including defaults and paging semantics. The description's field list does not add meaning about how those parameters behave, so the baseline of 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 and resource ('List the practice's physicians'), clarifies the synonym 'providers', and enumerates the fields returned, so the agent knows exactly what comes back. It reads clearly against the sibling list_* tools (patients, appointments, practices) without needing an explicit contrast.

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?

There is no when-to-use guidance, no mention of when to prefer this over another endpoint, and no note on whether the filters (npi, first_name, last_name) should be combined or when to page. Usage is only implied by the name.

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