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

readOnlyHint=true already declares this is a safe, non-mutating read, so the safety profile is covered by structured data. Beyond that the description adds no behavioral context at all: no note on pagination behavior, default result size, maximum result window, sort semantics, or permission requirements. It essentially restates the schema's id/query split rather than adding new behavioral information.

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 compact sentence, front-loaded with the verb and resource, that encodes the tool's two operating modes without filler. Nothing redundant and nothing padded.

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 leaves the agent guessing about the shape of returned records and about pagination or result-size behavior. Annotations cover the read-only safety question, but the description is thin for a list/query tool that returns an unspecified structure.

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 skip, limit (1-500 with clamping), sort ('-' prefix), and query (MongoDB-style filter with example) are already well documented in the schema. The description contributes only the id-vs-query distinction, which the schema already states for the id parameter, so it does not meaningfully extend parameter meaning.

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 (LimRewardEntry), and splits the tool into its two concrete modes: single-record fetch by id vs filtered list query. Among many identically patterned query_* siblings this is enough to identify exactly which resource collection is being read, though it says nothing about what a LimRewardEntry is or contains.

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 clause 'pass id for one record, or query for a filtered list' is real mode-selection guidance an agent can act on. However, there are no exclusions, no prerequisites, and no mention of the sibling tools or of what happens if both id and query are supplied — the routing is implied rather than fully specified.

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