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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description carries a lighter burden. It adds the single-vs-list behavioral distinction, but says nothing about default result size, clamping, or pagination behavior beyond what the annotations and schema supply. Adequate but thin.

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 compact sentence with the primary action front-loaded and the two modes stated in the order an agent would evaluate them. No filler, though the brevity also means few marginal details are conveyed.

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 query tool with annotations covering safety and no output schema, the description is minimally sufficient: it conveys lookup vs. list intent. It leaves gaps around the nested MongoDB-style query filter semantics, field projection behavior, and what a result set looks like, which the schema only partially covers.

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 explains id, skip, sort, limit (with clamping and defaults), and query. The description only restates the id/query modes and adds no syntax, format, or interaction details (e.g., whether id ignores query). Baseline 3 applies when the schema does the heavy lifting.

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 ('LimStoreReview records'), and the resource name alone separates it from the ~40 sibling query_* tools. It also distinguishes the two operating modes (single record by id vs. filtered list via query). It stops short of 5 because it never articulates anything resource-specific about LimStoreReview that would help an agent choose among overlapping data sources.

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 clause 'pass id for one record, or query for a filtered list' gives real mode-selection guidance: id implies single-fetch, query implies list. However, there is no when-to-use/when-not framing relative to alternatives, no note on combining id with query, and no guidance on which fields are worth filtering by.

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