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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the two-mode behavior (one record vs list), but does not mention default limit of 50, clamping of out-of-range values, or pagination behavior — all of which live only in the schema.

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 efficient sentence with the primary mode-selection rule front-loaded. No filler, though it is arguably too terse for a 6-parameter 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 read-only entity lookup with 83% schema coverage and no output schema, the description is serviceable but thin: it omits pagination defaults and the fields projection, leaving the agent to read the schema to call it correctly.

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 baseline is 3. The description only references id and query, adding no semantics for fields (the one underspecified parameter) or for combining skip/limit/sort.

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+resource ('Find LimFavorReply records') and distinguishes the two retrieval modes (single by id vs filtered list). It does not explicitly differentiate from the ~70 sibling query_lim* tools, though the entity name in the tool name carries that differentiation.

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 description implies when to use id vs query (single record vs filtered list), which is real guidance. It offers no exclusions, no mention of pagination/sort usage, and no alternatives — though for a uniform CRUD-family read tool there are no real alternatives to route to.

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