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

Annotations already cover readOnlyHint and openWorldHint, so the safety profile is known. The description adds non-obvious behavior beyond that: no quota is consumed (meaningful next to get_lab_quota) and the saved note text is untrusted user content that may be mistaken, which is important for downstream agent behavior.

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, each load-bearing: purpose, usage ordering, trust/quota caveat. Nothing is padded, and the critical warning is not buried behind boilerplate.

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 list tool with two fully described optional parameters, no output schema, and annotations covering the safety profile, the description covers purpose, ordering, cost, and content trust. Return shape/ordering is left implicit, which is the only remaining gap.

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 both 'top' (default 10, max 50) and 'pair' are fully documented in the schema. The description adds no filter syntax, format, or ordering semantics beyond what the schema already provides, so the 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 and resource ('Reads this account's saved laboratory conclusions') plus the distinguishing payload ('server-verified source snapshots'). It is clearly separable from list_lab_searches and get_lab_results, though it never names those siblings outright.

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?

'Read them before proposing another search' gives a concrete ordering directive that tells the agent when to reach for this tool. It does not name an explicit alternative tool or state exclusions, so it stops short of the 5 bar.

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