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

Annotations declare idempotentHind and non-read-only, and the description goes beyond them by describing IMAP validation before encrypted storage, the success return shape, and prerequisites. This gives the agent a clear behavioral model of what happens on success. No contradiction with annotations.

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?

Six short sentences, each carrying distinct value: purpose, validation/storage, use case, how to generate the password, IMAP prerequisite, and success response. Front-loaded with the core action and 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 a write tool with no output schema, it covers prerequisites, return contract, and lookup path for required IDs, so an agent can call it correctly. Remaining gaps like failure handling are minor given the idempotent annotation. Complete enough for autonomous invocation.

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% and the schema already documents appPassword format, googleAccountId lookup, email verification, and workspaceId defaulting. The description mostly repeats or echoes those schema notes (e.g., list_integrations, Google App Passwords page), adding little new parameter-specific meaning beyond what the schema already 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?

States a specific verb ('Set or update') and resource ('Google App Password for a connected Google account'), plus the validation and storage behavior. This clearly distinguishes it from other set_* siblings like set_private_proxy and positions it as the prerequisite for warmup features.

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?

Explicitly says this is required for email warmup (MailReach integration) and future IMAP features, giving concrete when-to-use context. It also directs the agent to campaignstack_list_integrations for valid IDs and lists IMAP/App Password prerequisites. It doesn't spell out when-not-to-use alternatives, so not a 5.

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