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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: data source ('CMS NPI Registry synced data'), cost ('$0.02 USDC per call'), and an illustrative output example showing counts and per-capita rates.

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 moderately concise and front-loaded with usage guidance. The example sentence and pricing note add useful context without excessive verbosity, though one more sentence on city parameter semantics would improve completeness.

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?

Given no output schema, the description explains what is returned (physician counts, market structure, example output), where the data comes from, and how much it costs. The main gap is the undocumented city parameter, but required parameters and expected use cases are clearly covered.

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 that results are 'by specialty and state' and gives an example using specialty and state, but it does not mention the optional 'city' parameter or define valid value formats for specialty/state.

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: 'Returns NPI registry physician counts and market structure by specialty and state.' It is clear that this tool is about physician supply/density, but it does not explicitly distinguish itself from sibling tools like get_physician_group_benchmark or get_cms_facility_benchmark.

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?

Explicitly opens with 'Use when assessing physician supply in a market, evaluating a healthcare network expansion, or benchmarking provider density,' which gives clear context for when to choose this tool. It does not mention when not to use it or name alternative tools.

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