list_testimonials

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

Annotations are absent, so the description carries the full behavioral burden. It implies a read operation but does not disclose the pagination cap (limit maximum 50), default page/limit values, filtering behavior, or return shape. The wording 'List all' sits awkwardly against the schema's 50-item limit, which is an undisclosed behavioral nuance.

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?

The description is a single, front-loaded, grammatically clean sentence with zero wasted words. It efficiently conveys action and resource. While the content is thin, the structure itself is appropriately sized for a simple list operation.

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 no output schema and no annotations, the description needed to carry more weight. It fails to mention return format, pagination defaults, ordering, or how the featured filter modifies results. For a tool with 3 optional parameters at 33% coverage, callers are left guessing about basic invocation behavior.

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 only 33%: only 'featured' has a schema description, while 'page' and 'limit' are undocumented. The description adds zero parameter context, so page/limit semantics, defaults, and their interaction remain completely unexplained. With coverage below 50%, the description was required to compensate and did not.

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?

"List all testimonials" states a specific verb (list) and resource (testimonials). The list verb distinguishes it from the singular get_testimonial and the mutating create/update/delete_testimonial siblings. Minor imprecision: "all" is undercut by the featured filter and pagination parameters in the schema, so the scope is not literally "all" in every invocation.

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 is given on when to use this tool vs. get_testimonial, how pagination should be handled across pages, or when the featured filter is appropriate. The bare statement merely implies 'use when you want testimonials' but provides no decision context or exclusions.

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