testimonial_request_email

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

With no annotations, the description carries the burden. It describes the tone ('warm, non-pushy'), the content structure (includes angle/prompt), and the draft limit behavior. However, it doesn't explicitly state whether the tool sends the email or just drafts it, though context implies drafting.

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 reasonably concise and front-loaded with the core action. It is a single paragraph, which could be more structured, but it effectively conveys key information without unnecessary words.

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?

Given the lack of output schema and annotations, the description is fairly complete. It explains the tool's purpose, usage timing, and a unique behavioral feature. It doesn't describe the return value, but for a generation tool this is usually acceptable.

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 100% with high-quality descriptions. The tool description adds marginal value, e.g., reinforcing that 'result_achieved' should be concrete and that 'angle_prompt' makes the ask easier. This meets the baseline but doesn't significantly enhance understanding beyond the 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 clearly states the tool's purpose: 'Write a warm, non-pushy email asking a past or current client for a testimonial, case study quote, or LinkedIn recommendation.' It uses specific verbs and resources, and explicitly distinguishes itself from the sibling 'client_offboarding_checklist_email'.

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 provides explicit usage context: 'Sent after a successful delivery or project milestone.' It clearly distinguishes this tool from the sibling 'client_offboarding_checklist_email', stating this is a standalone, full-effort ask. It also includes a behavioral note about not counting against draft limits.

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