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

readOnlyHint=true already declares this is a safe read, so the safety burden is covered by annotations. The description adds the two access modes, which is useful, but says nothing about pagination defaults, clamping of limit, or result shape. Adds some value over annotations, no contradiction.

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, front-loaded with the verb and resource, with the mode selection as the trailing clause. Zero filler and nothing that could be trimmed without losing signal.

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 no output schema, the description covers both invocation paths and the schema handles parameter semantics. Return shape and pagination behavior are the only gaps, and those are partially inferable from limit/skip descriptions, so this is nearly complete.

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 schema already documents skip, sort, limit, query, and fields in detail (including the 1-500 clamp and default of 50). The description's id/query distinction largely restates the schema's own "Fetch one record by id; omit to query many". Baseline 3 is appropriate.

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 LimFamilyUsage records") and splits it into two modes: single-record by id and filtered list by query. The entity name in the tool name already differentiates it from the ~45 sibling query_lim* tools, so no extra sibling routing is needed. It's clear, though it doesn't characterize what a LimFamilyUsage record represents.

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 which mode to use: "pass id for one record, or query for a filtered list." That is real when-to-use guidance covering the primary decision. It stops short of exclusions or advice on combining the modes (e.g. id with sort/limit is meaningless), so it isn't a full 5.

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