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

readOnlyHint=true already establishes this as a safe read operation, so the description need not restate safety. It adds the dual-mode behavior, but says nothing about default limit behavior, clamp semantics, or that combining id with query/filter params is handled — those live only in the schema. Adequate but not rich.

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 immediately followed by the mode-selection rule. Zero filler; every clause carries information.

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 6 parameters, a nested query object, and no output schema, the description covers the essential decision (id vs. query) and the schema carries parameter detail. The missing piece is what the response looks like for the list mode, but with no output schema that is a minor omission.

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 in detail (including the MongoDB-style filter example and the clamp behavior). The description only names id and query, adding no syntax or format information beyond the schema. Baseline 3 is correct.

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 (LimTask records), and explains the two operating modes (single record by id vs. filtered list via query). It does not differentiate from siblings beyond the resource name, but given the ~70 parallel query_lim* tools, the resource name is the only meaningful axis of distinction.

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 parameter selects which mode: 'pass id for one record, or query for a filtered list.' That is clear conditional guidance, though it offers no exclusions (e.g., what happens if both id and query are supplied) and no guidance on pagination or sort ordering.

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