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

With readOnlyHint=true already declaring the safe-read profile, the description's only addition is the id-vs-query mode split. It says nothing about result ordering, default page size, clamping behavior, or what a LimCreditUsage record contains; those gaps are partly covered by the schema's own parameter notes rather than the prose.

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 sentence, front-loaded with the resource and then the two modes. Nothing is redundant with the schema and there is no filler.

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 generic read tool with six optional params and no output schema, the description covers how to call it but not what comes back or what the record type represents (e.g., credit usage fields an agent might filter on). It is adequate to invoke correctly, but thin for interpreting results.

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 high (83%), with limit/default/clamping, skip, sort prefix, and the MongoDB-style query example all documented inline. The description adds no parameter meaning beyond that, so the 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 gives a concrete verb ('Find') and names the resource ('LimCreditUsage records'), plus the two retrieval modes (single by id, filtered list via query). It omits any differentiation from other siblings, but the resource name in the tool name and description is specific enough to separate it from the ~115 other query_lim* siblings.

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 does state the mode-selection rule ('pass id for one record, or query for a filtered list'), which is the most important when-to-use decision. However, it gives no guidance on combining or omitting the pagination parameters, no prerequisites, and no explicit alternative tool to reach for.

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