list_providers

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so safety is covered. The description adds one genuinely useful behavioral fact beyond that: results are paginated and the caller must follow 'next_offset' for subsequent pages. It does not mention page sizing behavior, ordering, or what happens when data is exhausted.

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 short sentences, front-loaded with the action and scope, and the second sentence delivers actionable pagination guidance. No filler or redundant restatement of the tool name.

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 simple read-only list tool with an output schema that presumably documents the page and next_offset fields, the description covers the essentials. The main gap is nothing on result ordering or total counts, which an agent might need to reason about pagination termination.

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 0%, so the description carries the burden, and it only partially compensates: 'one page' and 'Follow next_offset' imply offset/limit paging semantics, but the description never names the limit or offset parameters, their defaults, or their maximums. The schema constrains values but provides no prose meaning.

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 uses a specific verb and resource ('Read one page of practice providers'), making the scope ('one page') explicit. The resource name alone distinguishes it from siblings like list_clinics or list_appointment_types, though it does not explicitly reference those siblings.

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 resource name: an agent needing provider records will find this appropriate. However, there is no explicit when-to-use versus alternatives guidance, no note on whether filtering exists, and no exclusion conditions.

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