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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'GET' and 'paginated,' adding the operation's API method. It does not disclose response shape or pagination defaults, but the read-only profile is already covered by 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?

Two short sentences, with the core purpose first and the endpoint second; no filler or repetition. It earns its length.

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 simple read-only list tool with fully documented parameters, the description conveys the essential context: what is listed and how it is retrieved/paged. It doesn't describe the response envelope, but the tool is simple and the annotations cover safety.

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 the baseline applies; the description only generically mentions 'filters' and 'paginated,' without adding per-parameter nuance. All seven parameters have individual descriptions in the schema.

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 concrete operation ('List'), a specific resource ('lab-test orders'), and the key capabilities ('filters, paginated'), with the API endpoint. This distinguishes it from sibling tools like vital_get_order (singular) and vital_list_lab_tests.

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 makes the listing context clear: use it when needing paged, filtered lab-test orders. It does not explicitly call out alternatives or when not to use it, but the singular get-order sibling is implicitly differentiated by 'orders'.

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