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

readOnlyHint=true already establishes this is a safe read, and the description adds the single-vs-list mode distinction. It does not disclose pagination behavior (skip/limit clamping), sort semantics, or return shape, so it adds modest value over 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 front-loaded sentence with zero waste; the primary discriminator (id) precedes the alternative (query).

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 tool with a nested query object and no output schema, the description leaves the filter syntax, sort conventions, field projection and pagination entirely to the schema. It is minimally adequate but does not round out the picture an agent needs.

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%, above the 80% threshold, so the schema already documents id, skip, sort, limit and query. The description's id-vs-query note largely restates the id schema description, adding little new meaning and nothing for fields or the nested query object.

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 ('LimAccount records') plus the two operating modes (single by id, filtered list). Differentiation from the many query_lim* siblings comes only from the resource noun, which is adequate here since the siblings share the same pattern, but the description does not explicitly distinguish itself.

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 tells the agent how to choose between the two behaviors: pass id for one record, or query for a filtered list. There is no statement of when not to use it or which sibling to prefer, so it stops short of a 5.

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