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

Annotations already declare this is a non-readonly, open-world, non-idempotent, non-destructive operation. The description adds meaningful behavior beyond annotations: the login is tested before saving, and warm-up starts the same day, which tells the agent about validation and a side effect.

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 short, front-loaded, and every sentence adds relevant information: purpose, validation behavior, password guidance, preset-or-host choice, and warm-up timing. No filler.

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?

For an 11-parameter mutation tool with no output schema, the description covers purpose, validation, and a key side effect, but leaves gaps around SMTP configuration details and what a successful connection returns. It is adequate but not fully 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 coverage is 64%, so several parameters are documented in the schema. The description adds useful meaning for preset versus host configuration and clarifies the app-password case, but it does not explain the SMTP-specific parameters or ports beyond what the schema provides.

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 verb and resource: connect a mailbox via IMAP + SMTP. It is clear what the tool does, but it does not explicitly differentiate itself from the sibling connect_zoho_mailbox beyond saying 'any mailbox'.

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?

It gives useful setup guidance such as using an app password for two-factor sign-in and choosing a preset or hosts, but it does not explicitly say when to use this tool versus connect_zoho_mailbox or test_mailbox. The usage context is implied rather than fully stated.

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