hcp_list_hcps

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

With no annotations provided, the description is the only safety/behavior source. It does add the important trait that the data are mock and not real providers, and 'List' implies a read-only operation, but it does not mention pagination, ordering, or output shape.

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?

Two short, front-loaded sentences cover the operation, filters, and the mock-data warning with no filler. Every sentence earns its place.

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 definition is adequate for a simple list tool, especially with the mock-data warning and schema-enforced filter constraints. It is not complete: without an output schema or annotations, it leaves out return-field and pagination details, and any differentiation from hcp_search.

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 only 40%, so the description must compensate. It names four filter parameters and spells out tier values (A|B|C), but it does not explain the limit parameter or clarify whether the listed filters combine or are mutually exclusive.

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 identifies the operation ('List') and resource ('Healthcare Professionals (HCPs)'), and lists the main filter dimensions. It does not explicitly distinguish this from the sibling hcp_search, so it stops short of full sibling differentiation.

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 filter list gives a clear implied use case—obtain a filtered collection of HCPs—but no alternative tools are named and there is no when-not-to-use guidance. Since hcp_search exists as a sibling, the description leaves some selection to inference.

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