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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful scope context (HRSA registration) and output field transparency, but does not mention behavior around pagination, the default exclusion of terminated entities, or open-world result variation. No contradiction with 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?

Three sentences each earn their place: the first defines scope, the second summarizes filters and outputs, and the third frames concrete use cases. The description is front-loaded with the core verb and resource, and contains no filler words.

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 no output schema, the description compensates by listing key returned fields (340B ID, start date, parent hospital, Medicare CCN, NPIs, contract pharmacy count) and answerable questions. It relies on the schema for defaults and limits, which is acceptable given the schema's richness; a short note about the active-by-default behavior would make it fully complete.

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 100%, so every parameter already has detailed meaning in the input schema. The description briefly restates filtering by state, type, and name, but adds no syntax, defaults, or format details beyond what the schema provides. This meets the baseline but does not elevate it.

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 states a specific verb ('Find') and a well-scoped resource ('340B drug pricing program covered entities registered with HRSA'), then enumerates entity types and outputs such as 340B ID, registration start date, and NPI numbers. It clearly conveys what the tool does, though it does not explicitly differentiate itself from the sibling b340_contract_pharmacies beyond the phrase 'how many contract pharmacies each one uses.'

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 closing sentence provides clear context for when to use the tool: answering which providers can buy drugs at 340B ceiling prices in a state, whether a named hospital participates, and when it joined. There are no exclusions or explicit comparisons to alternative tools, but the intended use is not left to inference.

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