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

No annotations are provided, so the description carries the full burden. It discloses the default status filter ('Designated'), the sort fields, and includes a price note. However, it does not mention pagination behavior (despite offset/limit in schema), rate limits, authentication requirements, or error handling. The description adds some context (e.g., 'mapped staffing-demand signal') but lacks comprehensive behavioral disclosure for a tool with no annotations.

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 a single dense paragraph that front-loads the purpose and key use case. Every sentence adds value: purpose, answers, filters, sort, default behavior, and price. There is no fluff. However, the price note could be considered extraneous for a description (better suited to metadata). Still, it is well-structured and efficient for an agent.

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 the tool's complexity (10 parameters, no output schema, no annotations), the description covers the essential aspects: what the tool does, typical filters, sort options, default behavior, and a use case. It lacks details on return format or pagination (though limit/offset are in schema). It also doesn't explain the meaning of HPSA scores beyond min/max. However, it provides enough context for an agent to select and invoke the tool correctly in most scenarios.

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 80% (8 of 10 parameters have descriptions in the schema). The tool description summarizes key filters (state, discipline, min_score, min_fte, rural_status, designated_since, status) and sort options, adding context like 'minimum HPSA score (0-26; higher = greater shortage)'. However, most of this is already present in the schema. The description does not clarify the meaning of 'sort' values beyond listing them. Baseline 3 is appropriate; the description adds marginal value.

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 finds HRSA Health Professional Shortage Areas by discipline, state, and shortage metrics. It specifies the verb 'Find', the resource 'Health Professional Shortage Areas', and lists key fields (Primary Care/Dental/Mental Health, HPSA score, FTE shortage). The use case is explicit: 'Powers medical & travel-nurse staffing.' This effectively distinguishes it from siblings like hcris, carecompare, and other healthcare tools.

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 explains what the tool does and lists filters (state, discipline, min_score, min_fte, rural_status, designated_since, status) and sort options. It mentions defaulting to currently-designated areas. However, it does not explicitly compare to sibling tools or provide when-not-to-use guidance. For example, it doesn't clarify when to prefer hrsa_healthCenters_search or carecompare tools. Still, the context is clear enough for typical use.

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