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

Annotations already establish a safe read-only profile, and the description adds real behavioral value on top: it disambiguates status values ('hidden' = rejected, 'draft' = abandoned review), discloses that long texts are truncated unless full_text is true, and notes 'words' always reflects the full count. Pagination via offset is also stated.

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?

Three dense sentences, front-loaded with the core action and free of filler. Efficient and readable, though quite terse relative to the size of the parameter surface it needs to support.

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 read-only list tool with no output schema, the description usefully flags a couple of return-shape quirks (text truncation, 'words' field), but with 17 parameters and no output schema it omits most parameter behavior and any picture of the returned record fields. Adequate but incomplete.

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?

With 17 parameters and only 41% schema description coverage, the description compensates for a few key ones (status, full_text, offset) but leaves most undocumented, including sort, limit, search, and the rating/date filters. It adds meaningful semantics for what it covers but is far from complete against a very wide schema.

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 opens with a specific verb set (search, filter, sort) and the resource (testimonials), so the operation is unambiguous. It doesn't explicitly differentiate from siblings like get_testimonial or moderate_testimonials, but the list/query intent is clear without opening a schema.

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?

No guidance on when to use this tool versus alternatives such as get_testimonial (single fetch) or moderate_testimonials. The status explanations describe domain semantics, not tool selection, so there are no when/when-not conditions or sibling routing.

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