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 restates the id/query selection but adds no behavioral context such as pagination defaults, clamping behavior, or result shape that would go beyond the annotations and 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 front-loaded sentence with no filler that covers both operating modes efficiently. It could still be marginally tighter and add one clause of return/pagination context without bloat.

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?

With 6 parameters, a nested MongoDB-style filter object, and no output schema, the description is adequate but thin: it does not mention pagination defaults, the 1-500 limit range, or that it returns a collection of records. The schema carries most of the load at 83% coverage.

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 most parameters (skip, sort, limit, query, id) are already documented in the schema, and the description only echoes the id/query distinction. The lone undocumented parameter, fields (projection), is not addressed in prose.

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 ('Find') and resource ('LimDevice records') and distinguishes the two access modes (single by id, filtered list by query). Differentiation from the 40+ sibling query_lim* tools comes only from the entity name in the title/name, which is the standard convention here, so it is clear but not reinforced in prose.

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?

Gives explicit conditional guidance for the two modes: 'pass id for one record, or query for a filtered list.' It does not say when to prefer this tool over adjacent ones or what happens if neither id nor query is supplied (required parameters are zero), leaving slight ambiguity.

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