List testimonials

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

Annotations cover read-only, idempotent, non-destructive. The description adds one meaningful behavioral note: output may contain personal data (customer name/email), which is genuinely useful. But it does not clarify pagination behavior, total counts, or result limits, leaving meaningful gaps for a 12-param listing tool.

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?

Single sentence, no filler, front-loaded with the core action. It is compact but at the cost of detail; reasonable for its length.

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 12-parameter tool with no output schema, the description is thin. It doesn't explain return shape (e.g., what 'total counts only the current page' implies), pagination usage, sort/order interaction, or the account/integration filters. It leaves the agent without enough to call it confidently.

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 42%, so roughly half the parameters are undocumented in the schema. The description lists filter categories (search, tag, approval, language, date/rating) but doesn't map them to specific parameters or explain semantics like 'exact configured private account profile label.' Baseline 3 is the ceiling given the description doesn't compensate for the coverage gap.

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 says it reads a 'native page' of testimonials and enumerates filter dimensions, but 'one native page' is unusual phrasing that doesn't clearly state whether pagination is supported (the schema has a 'page' param, so it must be). It never explicitly distinguishes from siblings like get_testimonial or export_testimonials.

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 versus get_testimonial (single fetch) or export_testimonials (bulk export). The reader must infer that this is the list/browse operation, but nothing is stated.

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