milestone_delivered_email

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

No annotations are provided, so the description must fully cover behavior. It describes the email content and purpose but does not disclose whether the email is sent immediately or saved as a draft, nor any side effects like logging. Behavior is somewhat implied but incomplete.

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?

Four sentences with no redundant elements. The first sentence front-loads the purpose, followed by details and sibling differentiation. Every sentence adds value without waste.

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?

Despite lacking an output schema, the description covers purpose, usage, and content well. It is sufficient for an agent to understand the tool's role. Minor gaps (e.g., whether the email is sent or drafted) prevent a perfect score, but for a straightforward email generation tool, it is largely complete.

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 clear parameter descriptions. The overall description adds context about the email's structure but does not provide additional meaning beyond what the schema already offers for individual parameters. Baseline of 3 is appropriate.

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 'Write the email sent when delivering a project milestone or phase' with a specific verb and resource. It explicitly distinguishes from sibling tools 'project_completion_email' and 'project_status_update', 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?

Provides explicit when to use (delivering a milestone/phase, not final delivery) and names alternative tools for other cases. Also adds a unique note about not counting against monthly draft limits, giving practical usage context.

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