Get Testimonial

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

Annotations already declare readOnlyHint and destructiveHint, so the safety profile is known. The description adds that the full record is returned as JSON, providing insight into the response format, and clarifies that lookup can be by id or slug. This adds value beyond the annotations.

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 two terse sentences that front-load the action and return type without extraneous details. It is minimal and every phrase contributes to understanding.

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 simple single-fetch tool with one parameter and no output schema, the description covers the core invocation and return behavior. Combined with strong annotations (read-only, idempotent), it provides enough context for an agent to use it correctly. The only minor gap is lack of error-handling details, but this is not essential for such a basic tool.

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?

The schema description for the 'id' parameter already states 'Testimonial id or slug', which fully covers the parameter meaning. The tool description repeats this information without adding new semantics, so it adds no additional value beyond the schema's 100% coverage.

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 clearly states the tool fetches a single testimonial by either id or slug, using the specific verb 'fetch' and distinguishing it from list_testimonials. It also specifies the return format as JSON, making the purpose unambiguous.

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 description implies the tool is for retrieving one testimonial rather than a list, which is supported by the required id parameter. However, it does not explicitly contrast with list_testimonials or mention when to use alternatives. The context is clear but lacks explicit exclusions, so it scores a 4.

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