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

readOnlyHint=true already establishes this is a safe read operation, so the description's burden is lower. It adds the useful behavioral fact that the tool returns either one record or a list depending on inputs, but says nothing about pagination behavior, result size, or empty-result handling.

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 tight sentence with zero filler, and the primary mode distinction is front-loaded immediately after the verb. Every clause earns its place.

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 read tool with no output schema, the description covers the core mode distinction and the schema covers the remaining mechanics at 83%. Only the 'fields' parameter and return-shape expectations are left implicit, which is a minor gap.

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 (only 'fields' is undocumented). The description restates the id-vs-query semantics but adds no format or syntax detail beyond what the schema provides, so baseline 3 is appropriate.

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 (Testimonial records), and distinguishes the two retrieval modes (single by id vs. filtered list). It's clearly the read counterpart to create_testimonial/update_testimonial/delete_testimonial, though it doesn't name those siblings explicitly.

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?

Explicitly routes the agent between the two modes: 'pass id for one record, or query for a filtered list.' That is clear usage context, but there is no guidance on exclusions or when to prefer an alternative approach (e.g., when not to use it, or relationships with sibling tools).

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