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

readOnlyHint=true already establishes the read-only safety profile, and the description adds essentially no behavior beyond it: no mention of result shape, sort/pagination behaviour, or what happens when id and query are combined. For a query tool with a nested filter object, the description carries little of the load.

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?

One tight sentence with the primary usage fork front-loaded and zero filler. It is efficient, though its brevity borders on under-specification rather than optimal density.

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 definition should explain at least the return shape and the precedence between id and query. It leaves both implicit, so an agent must infer behaviour that the description could cheaply have stated.

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 coverage is 83%, so parameters are largely self-documenting, including the id 'omit to query many' note and the MongoDB-style filter example. The description only restates the id-versus-query dichotomy already present in the schema and adds no meaning to skip, sort, limit, or fields.

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 (LimForm records), and the two operating modes are clear. However, it never distinguishes itself from the very similar sibling query_limformresponse, which an agent could easily confuse with form records versus form submissions.

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' gives implied guidance on which parameter path to take, but says nothing about when to prefer this tool over query_limformresponse or how id and query interact if both are supplied.

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