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

The description adds context beyond the readOnlyHint/destructiveHint annotations by revealing the data source (CMS NPI Registry synced data) and the nature of the output (counts and market structure). It does not contradict annotations, and the example provides concrete insight into the output format and interpretation. No annotation contradiction.

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 concise, front-loaded with use cases, and every sentence adds value: the use context, the data returned, and a concrete example with interpretative guidance. No fluff 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?

The description is complete enough for a simple query tool with two required parameters. It explains the data source, the return type, and provides an example that illustrates the output and its business interpretation. There is no output schema, so the example helps fill that gap, though it doesn't detail edge cases or error conditions.

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 must compensate. It explains the 'specialty' and 'state' parameters by noting the output is 'by specialty and state' and gives an example ('Illinois cardiology'). However, it does not mention the optional 'city' parameter at all, leaving its semantics unspecified. The description partially compensates but not fully.

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 clearly states the tool's function: 'Returns NPI registry physician counts and market structure by specialty and state.' It provides a specific verb ('Returns'), a specific resource (NPI registry physician counts), and scope (by specialty and state). This distinguishes it from siblings like get_npi_provider_verification (individual verification) and get_physician_group_benchmark (group-level benchmarking).

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 description explicitly lists when to use the tool: 'assessing physician supply in a market, evaluating a healthcare network expansion, or benchmarking provider density for population health strategy.' It gives clear context but does not explicitly mention when not to use it or name alternative tools, so it's not a full replacement for sibling differentiation.

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