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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description nonetheless adds essentially nothing beyond the structured fields: the id-versus-query branching it states is already written verbatim in the schema property descriptions, and there is no mention of pagination defaults, result caps, or cost of an unbounded query.

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 with zero filler, front-loading the resource and then the two mode branches in the order an agent would consider them. Nothing could be removed without losing routing 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?

There is no output schema, and the tool has six parameters including a nested free-form MongoDB filter object, so the description should ideally say something about return shape or how the filter interacts with sort/limit. The schema covers most of that ground, leaving the definition adequate but with real gaps for a query tool with a nested filter.

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 carries the parameter burden (defaults, clamping, sort prefix syntax, MongoDB-style filter example). The description only names "id" and "query" and adds no format or constraint detail beyond them. Baseline 3 applies 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 concrete verb and resource ("Find LimDrop records") and distinguishes the two operating modes: fetch-by-id versus filtered query. Among ~120 sibling query_lim* tools, the resource noun itself is the differentiator, so an agent can route on name + description without opening the schema. It stops short of a 5 because it never states what a LimDrop record is or what distinguishes this collection from adjacent ones.

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?

Gives explicit conditional guidance inside the tool: pass "id" for one record, use "query" for a filtered list. That resolves the main ambiguity an agent faces with six optional parameters. It offers no when-to-use versus alternatives or prerequisites, so it is clear context without exclusions.

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