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

The readOnlyHint already declares this is a safe read, so the safety burden is lifted. The id-vs-query mode routing is a useful behavioral note, but it largely restates the schema's own id description, and nothing is said about pagination limits or result shape beyond what structured fields provide.

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 the two modes stated up front and no wasted words. It is efficient, though its brevity is part of why coverage elsewhere is thin.

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 6-parameter query tool with a nested MongoDB-style filter object and no output schema, the description is minimal. It routes between modes but leaves filter semantics, sorting, and pagination behavior to the schema, which covers most but not all of the surface.

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 id, skip, sort, limit, and query with formats and clamping behavior. The description adds only the id-vs-query routing, which is redundant with the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (LimCall records), and clarifies the two operating modes (single by id vs filtered list). It does not explicitly distinguish itself from the many sibling query_lim* tools, but the resource name carries that differentiation inherently.

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 tells the agent to pass id for one record or query for a list, which is mode-selection guidance, but gives no guidance on when to prefer this tool over sibling query tools or any prerequisites. Usage is implied rather than fully spelled out.

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