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

readOnlyHint=true already tells the agent this is a safe read. The description adds the id-vs-query behavioral split but omits pagination behavior, the default limit of 50, clamping of out-of-range limits, and what a bare call with no arguments returns. Useful but thin beyond what annotations and schema already declare.

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?

A single, front-loaded sentence with zero waste; the mode distinction is stated up front. It is arguably too compressed — a few more words on default behavior would earn their place without bloat.

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 read-only record-fetch tool with no output schema, six optional parameters, and an 83%-documented schema, the definition plus schema give the agent everything needed to construct a correct call: id for one record, query for many, and documented paging/sort fields.

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 83%, so the schema already documents id, skip, sort, limit, and query with formats and defaults. The description restates the id/query distinction but adds no syntax, semantics, or examples beyond the structured fields, so 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 ('Find') and resource ('LimHealthRecord records') and explains the two operating modes: single-record lookup by id versus filtered list via query. It does not differentiate itself from the ~110 identically-named sibling query_* tools beyond the resource name, but within this family the resource name is the only meaningful differentiator.

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?

Gives one conditional rule — pass id for one record, query for a filtered list — which helps the agent choose between parameter modes. It says nothing about when not to use the tool, what happens when neither id nor query is supplied, or how it relates to other record-fetching paths.

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