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 dual-mode behavior (single vs. filtered list), which is genuinely useful context, but says nothing about pagination, sort defaults, or what happens when both id and query are supplied.

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?

One sentence, zero waste, and the mode-selection rule is front-loaded. Nothing to trim.

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 rich schema descriptions and an existing readOnlyHint, the description covers both invocation modes adequately. Only remaining gap is behavior when id and query are combined, or interaction with skip/sort.

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, query, and fields. The description only echoes the id/query distinction the schema already spells out, adding no format, syntax, or defaulting detail beyond it.

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 (LimAiDownload records) plus the two access modes. This distinguishes it from the ~70 sibling query_lim* tools only by the resource name, which is inherent to the family pattern rather than an explicit differentiation sentence.

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?

Explicitly tells the agent the two modes: pass `id` for a single record, pass `query` for a filtered list. No guidance on when to prefer one mode over another or on combining the two, but the mode selection is unambiguous.

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