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

Annotations already declare readOnlyHint=true, so the safe read-only nature is covered structurally and "Find" is consistent with it. The description adds nothing about result shape, whether id takes precedence over query, or how skip/limit interact with a filtered query. With annotations carrying the safety profile, this 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, front-loading the resource and then the two invocation modes. Nothing is repeated or 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?

For a read-only query tool with 83% schema coverage and no output schema, the essentials are present: what it fetches and the two modes of calling it. The remaining gaps (return shape, default limit behavior, precedence when both id and query are given) are modest but real for a tool with a nested filter object.

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%, so the schema already documents id, skip, sort, limit, and the MongoDB-style query filter. The description reinforces the id-vs-query relationship but adds no syntax, format, or precedence detail beyond what the schema states. 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?

The description pairs a specific verb ("Find") with a specific resource ("LimCreditWallet records") and distinguishes the two retrieval modes: single-record by id versus filtered list by query. Sibling tools follow the identical query_lim<resource> pattern, so resource naming alone differentiates it adequately, though nothing explicit is said about the siblings.

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 clear mode-selection guidance ("pass id for one record, or query for a filtered list"), which is genuinely useful for choosing among its own parameters. However, it offers no when-not-to-use guidance, no mention of the sibling query tools, and no prerequisites or edge cases such as what happens when both id and query are supplied.

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