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

Annotations already declare readOnlyHint=true, so the safety burden is light; the description still adds value by disclosing that filters are conjunctive and that continuation reuses the page parameter rather than a cursor. It also flags the record set as health data, which is meaningful behavioural context for an agent handling the results.

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 short sentences, front-loaded with the resource and scope, followed by filter semantics and pagination. Nothing is wasted and the endpoint reference is compact.

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?

For a 12-parameter list tool with no output schema, the description covers scope, filter semantics, pagination and data sensitivity, and the schema covers every parameter. Only a hint about what a coverage record contains or the default sort would improve it further.

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 coverage is 100%, so all 12 parameters are documented in the schema itself, including the next_page-to-page hint and the sort enum. The description only adds the AND-combination rule for filters, which is useful but marginal over an already complete schema — baseline 3 applies.

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 ('List or search') and resource ('patients' health fund membership and claim details'), and the 'HEALTH DATA' tag flags sensitivity, which no sibling does. It implicitly separates itself from halaxy_get_coverage by being plural/searchable, but never names the single-record alternative explicitly.

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?

'Filters combine with AND' and 'Paged: pass next_page as page' give real usage mechanics for querying and paging. However, there is no guidance on when to use this list tool versus halaxy_get_coverage for a known id, nor any prerequisite or exclusion information.

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