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

The readOnlyHint=true annotation already establishes this is a non-mutating read, and the description's "Find" wording is consistent with that. It adds the id-vs-query branching, but says nothing about the shape of returned records, default result window behavior, or cost/rate characteristics beyond what the schema states.

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 the resource first and the two invocation modes second; there is no filler, hedging, or redundant restatement of the tool name.

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 MongoDB-style filter and no output schema, the definition covers the core invocation pattern but leaves the return shape and the interaction between query, sort, skip, and limit to the schema. Adequate, but not complete for an agent needing to reason about result paging or filter syntax.

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 parameters are largely self-documenting; the description's contribution is clarifying that id fetches one record while query produces a filtered list. That meaning is largely duplicated in the schema's own id text ("Fetch one record by id; omit to query many"), so the added value is marginal and a baseline 3 is appropriate.

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?

The description names a specific verb ("Find") and resource ("LimKidProfile records") and splits the operation into two recognizable modes: single record by id, filtered list by query. It is clear what the tool does, though differentiation from the many sibling query_lim* tools rests entirely on the resource name rather than any explicit statement.

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?

It gives implied usage guidance by saying "pass id for one record, or query for a filtered list," which tells an agent which parameter selects which behavior. It does not say when another tool would be preferable, nor does it address combining id with query/skip/limit or what happens with no parameters at all.

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