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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the id-vs-query mode split but says nothing about default projection, result caps, or pagination behavior beyond what the schema states. Adequate, not rich.

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 that front-loads the verb+resource and then the mode split. No filler, no redundancy.

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 6-parameter tool with a nested query object and no output schema, the description is thin: it does not describe what a returned record looks like, default field projection, or how the nested MongoDB-style filter is validated. The schema carries most of the load, so this is minimum viable rather than complete.

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 documents id, skip, sort, limit, and query in detail. The description's id/query contrast largely restates the schema's own 'omit to query many' note, adding little new meaning. Baseline 3 is correct.

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 (LimPhoto records), and splits the two invocation modes (single by id vs filtered list by query). It does not differentiate from the ~45 sibling query_lim* tools beyond the resource name, but that name is the only real distinction available.

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?

Clearly tells the agent which parameter selects which mode: 'pass id for one record, or query for a filtered list.' That is actionable routing guidance, though it offers no exclusions or advice on when to prefer a sibling tool.

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