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

The readOnlyHint annotation already declares this is a non-mutating read, so the description's burden is lower. It adds only the single-vs-many behavioral fork; it says nothing about result ordering defaults, pagination interaction, or how an empty query behaves. That is adequate but not rich.

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 with zero filler, and the two operational modes are front-loaded. It could be marginally sharper by naming the resource's domain, but nothing is wasted.

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?

Six parameters with a nested MongoDB-style filter make this a moderately complex tool, and there is no output schema to explain returns. The description covers the mode split but leaves the shape of results, and the interaction between limit and skip in multi-page retrieval, entirely to the schema.

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, query, and fields in detail, including the 1-500 clamp and descending prefix. The description only restates the id/query split, adding no syntax or filtering nuance beyond the schema.

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 ("Find LimPayLedgerEntry records") and immediately distinguishes the two retrieval modes: single-record lookup via id vs. filtered list via query. The resource name alone separates it from the many sibling query_lim* tools, so no explicit sibling differentiation is needed, but it also adds none.

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" tells the agent exactly which parameter selects which behavior, and "omit to query many" in the schema reinforces it. There are no exclusions or prerequisites stated, but for a read-only query tool there is little else an agent must rule out.

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