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

No annotations provided. The description explains it is a query tool returning specific fields and mentions price per row. It does not declare read-only nature or potential side effects, but the context implies no destructive actions.

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 (two sentences) and front-loaded, immediately stating the tool's purpose. Every sentence adds value, including pricing information.

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 10 parameters and no output schema, the description mentions key return fields (service area, IMU score, geography, dates) and provides business context. It could be more complete by listing all return fields, but is adequate.

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?

All parameters are described in the input schema with examples. The description adds value by explaining IMU score meaning (LOWER = more underserved) and date format, going beyond the schema.

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 searches HRSA Medically Underserved Areas/Populations (MUA/P) and lists searchable fields. It distinguishes from sibling hrsa_hpsa_search by focusing on MUA/P data.

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 specifies searchable criteria and return fields, and mentions use cases (safety-net / FQHC territory). However, it lacks explicit exclusions or comparisons to alternatives like hrsa_hpsa_search, which would improve guidance.

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