send_email

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

No annotations are provided, so the description must carry the full burden. It reveals the core behavior (immediate send, no draft) but does not disclose other traits like authentication requirements, rate limits, or whether attachments are supported.

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 clear sentence followed by a bullet list of parameters. Every part is useful and well-organized, with no wasted 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?

The description covers purpose and all parameters. The existence of an output schema reduces the need to explain return values. However, it could mention potential errors or prerequisites (e.g., authentication) for full completeness.

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 description includes a full list of all 7 parameters with Vietnamese explanations, adding meaning beyond the schema's titles and defaults. Schema description coverage is 0%, so the description compensates adequately.

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 composes and sends an email immediately, with the explicit note 'không lưu nháp' (no draft saved), differentiating it from siblings like create_draft and send_draft.

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 usage for immediate sending without saving drafts, but does not explicitly name alternatives or state when not to use this tool. Siblings like create_draft and send_draft exist, but no comparative guidance is provided.

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