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

The readOnlyHint=true annotation already establishes the safety profile. Everything the description adds  single-record vs. list mode  is already stated verbatim in the schema's 'id' description, so nothing new is disclosed about result size, default ordering, or the distinction from the webhook-log sibling.

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 resource first and the two modes second. No filler, no redundancy within the text itself.

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 tool with 6 params, a nested query object, and no output schema, the definition is minimally adequate. It never explains what a LimWebhook record contains, how it differs from a webhook log, or what a list response looks like, which matters given the dense sibling set.

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 explains id, skip, sort, limit, query, and gives a MongoDB-style filter example. The description reinforces the id-vs-query mode split but adds no syntax, defaults, or meaning beyond the schema; 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?

States a specific verb and resource ('Find LimWebhook records') and splits the two operating modes (single id vs. filtered query). It is clear in isolation, but with ~130 sibling query_lim* tools  including the very close query_limwebhooklog  it does nothing to distinguish webhook records from webhook logs.

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?

'pass id for one record, or query for a filtered list' implies the two calling modes, which is useful. However there is no when-to-use guidance against alternatives such as query_limwebhooklog, and no note on when to prefer fields/sort/skip over a bare query.

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