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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent), leaving the description to explain what actually happens. It does add real side-effect context: a contact record is created and the email is ingested as the conversation's first message, plus the non-obvious negative disclosure that no email is sent to the sender. It omits the non-idempotency implication (re-running may create a duplicate contact) and whether the item leaves the external mail list.

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?

Two sentences, no filler, and the core effect (what the email becomes) is front-loaded before the reassuring 'nothing is sent' clarification.

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?

With no output schema and only generic annotations, the description carries most of the burden, and it covers the essential outcome and the key side effect. It is slightly thin on post-conditions for the original external mail record and on repeat-invocation behavior, but nothing essential for calling the tool correctly is missing.

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?

There is a single required parameter and the schema description coverage is 100%, with emailId documented as coming from list_external_mail. The description adds nothing beyond the schema, which is the expected baseline when the schema already does the work.

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 states a specific transformation: an External email becomes the first message of a conversation and its sender becomes a contact. That distinguishes it from sibling mutations such as delete_external_mail or mark_external_mail_spam, though it never names an alternative explicitly and the 'move to inbox' framing in the name is only loosely echoed.

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?

Usage is implied through the scenario described (an External email exists and you want it turned into a conversation), and 'Nothing is sent to them' implicitly routes the agent away from reply_to_conversation. There is no explicit when-to-use versus when-not-to-use statement or prerequisite (e.g. does the mail need to be unread, non-spam).

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