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

readOnlyHint=true already declares the read-only safety profile, and 'Find' is consistent with it. The description adds nothing beyond annotations: no note on default page size behavior, clamping, ordering when sort is omitted, or result shape. Adequate but thin given annotations already carry the safety signal.

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 resource and immediately followed by the mode split. No filler, no restatement of the 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?

Six parameters with a nested MongoDB-style filter and no output schema, so the description should do more. It omits the 'fields' projection semantics entirely and gives no hint about what a returned record looks like or how results are ordered by default.

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 query with useful detail (including the '-' descending convention and clamping). The description's id/omit framing largely restates the id parameter's own schema text, and it says nothing about the undocumented 'fields' array or the nested query object's supported operators.

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 (LimNowCoinAccount), and explicitly distinguishes the two access modes: single record by id versus filtered list by query. It does not need sibling differentiation since no other query_lim* tool targets this resource, but it also doesn't position itself relative to related entities like query_limnowcointx or query_limnowcoinlink.

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?

Clear selection rule between the two modes ('pass id for one record, or query for a filtered list'), which is the main invocation decision for this tool. No guidance on combining id with query, on pagination strategy, or on which sibling to use for related coin data.

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