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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only the id-vs-query mode split and nothing about pagination defaults, clamping behavior, or result shape — all of which live in the schema rather than here. Adequate but no value beyond structured fields.

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 filler; the mode distinction arrives immediately. Appropriate size for a simple query tool.

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 covers only the top-level mode choice. It says nothing about the fields projection, the meaning of the returned collection, or how sort/clamping interact — the schema carries most of that, but the nested query filter semantics deserve at least a nod.

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, and limit with useful detail (defaults, clamping, prefix syntax). The description repeats the id-vs-query distinction that the schema's own id description already states, and adds nothing for the undocumented 'fields' projection parameter. Baseline 3 applies.

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 uses a specific verb ('Find') plus the exact resource ('LimPayTransaction records') and distinguishes the two modes of operation (single by id vs filtered list). It is clear enough to separate this tool from the mass of query_lim* siblings because the resource name is explicit, though it doesn't note how it differs from related ones like query_limpaylink or query_limpaysettings beyond the entity.

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 states the selection rule for the two invocation modes: pass 'id' for one record, 'query' for a filtered list. That is concrete operational guidance. What's missing is any context on when this entity is the right target versus sibling payment tools, 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.