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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It adds the dual-mode behavior and the fact that omitting id switches to list mode, but says nothing about pagination defaults, result caps, or how the filtered list behaves when query is absent. Adequate but thin beyond the annotation.

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 sentence, front-loaded with the verb and resource, and the mode-selection clause is placed immediately after. No filler, no redundancy.

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 6-parameter read tool with a nested query object and no output schema, the description plus the rich schema fields cover what an agent needs to invoke it correctly. Return shape and default-limit behavior are left implicit, which is a minor gap given no output schema exists.

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 83% and the parameter descriptions already explain skip, sort, limit (with clamping and default), and the MongoDB-style query shape. The description confirms id/query semantics but adds no syntax or format detail beyond what the schema documents, 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?

Names a specific verb ('Find') and resource ('LimStoreApp records') and clearly splits the two operating modes (single record by id vs filtered list via query). It does not differentiate itself from the forty-plus sibling query_* tools beyond the resource name, but within its own family the purpose is unambiguous.

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?

Explicitly states the selection rule between modes: pass id for one record, use query for a filtered list. There is no guidance on exclusions or when another tool would be a better fit, but the branch condition an agent actually needs is present.

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