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

The readOnlyHint=true annotation already establishes this as a safe read, and the description adds nothing beyond it: no pagination behavior, no default limits, no auth requirements, no note about how large result sets are handled. It essentially restates the operation shape the annotations and schema already imply.

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 zero filler that immediately communicates the two operating modes. It is efficient, though arguably too terse for a tool with a nested MongoDB-style filter object.

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?

With six parameters, a nested query object, and no output schema, the description is minimally adequate: the schema documents most parameters, so an agent can call it, but the description leaves query-shape examples, sorting/paging interaction, and default behavior entirely to the schema.

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%, well above the threshold where the schema carries the parameter burden. The description's mention of 'id' and 'query' merely duplicates what the id and query schema descriptions already say, adding no syntax or format detail of its own.

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') plus the resource ('LimBan records') and names the two access modes (by id, or filtered list). It distinguishes itself from the many query_lim* siblings only by the resource noun, which is adequate here since each sibling targets a distinct collection.

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?

The description explains the id-vs-query branch ('pass id for one record, or query for a filtered list'), which is genuine usage guidance for choosing a parameter. However, it offers no when-to-use context, prerequisites, or comparison against any alternative tool.

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