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

The read-only framing ('Find') is consistent with readOnlyHint=true, so no contradiction. Beyond that the description adds only the id/query branching; it says nothing about pagination behavior, whether the query object supports operators, or what an empty result looks like — topics the agent would need with no output schema available.

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 that front-loads the resource and then the two usage modes. Nothing to trim and nothing important buried.

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. It omits what the query object syntax supports, what fields are returned by default, and how the 'fields' projection behaves, leaving real gaps for a flexible query tool.

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 the schema carries most parameter meaning and a 3 is the baseline. The description echoes the id and query semantics already in the schema but adds nothing on skip/limit/sort, and the 'fields' array has no description in either place.

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?

The description names a concrete verb ('Find') and resource ('LimTimeSnapshot records') and splits the two operating modes: single-record lookup by id versus filtered list via query. It does not distinguish this tool from the ~100 sibling query_lim* tools, but the purpose itself is unambiguous.

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?

It gives mode-selection guidance ('pass id for one record, or query for a filtered list'), which tells the agent how the two entry paths differ. It offers no guidance on when to prefer this tool over sibling query tools, no exclusions, and no note on what happens if both id and query are supplied.

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