send-email

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

With no annotations, the description carries full burden. It states the tool composes and sends an email, but does not disclose behavioral traits such as whether the email is actually transmitted immediately, failure modes, rate limits, or if it requires authentication. The description is minimal and lacks transparency.

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 short sentence, which is concise, but it lacks structure and fails to front-load key information beyond the purpose. It could be expanded with minimal effort to include usage hints or constraints without becoming verbose.

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 tool has 6 parameters (3 required), no output schema, and no annotations, the description is insufficient. It does not explain return values, error conditions, or how the email sending process works (e.g., synchronous vs. asynchronous). The minimal description fails to cover necessary context for reliable use.

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 coverage is 100% (all 6 parameters have descriptions). The description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate as the schema already documents parameter semantics 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 'Composes and sends an email' clearly states the verb and resource, but it is generic and does not differentiate from other email-related sibling tools like list-emails, search-emails, or mark-as-read. A more specific description would improve clarity.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., need a configured email account), nor when not to use it (e.g., for reading or listing). Sibling tools exist but are not referenced.

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