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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds substantial non-annotation behavior: a 15-minute provenance_token window valid on any replica, the exact consequence of a missing receipt (values labeled unverified_model_data), the mandatory verbatim attribution footer, and a data-accuracy contract.

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?

Purpose is front-loaded in the first sentence, which is good. However the body is dense and runs long, with multiple interleaved contracts (chart_render provenance, footer handling, accuracy rules) that dilute the core read/search/list message rather than each earning crisp placement.

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 7-action connector with full schema coverage and no output schema, the description covers downstream integration and data-handling contracts well. Auth prerequisites are left to the schema, which is acceptable, and no return values need restating since no output schema exists.

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 action enum plus params object fully document all inputs, so the baseline of 3 applies. The prose adds no parameter-level detail (no formats, syntax, or defaults) 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?

The opening sentence names a specific verb set and resource ('read, search, and list emails from any connected inbox') across Gmail and Outlook, so the agent knows what the tool does. It does not, however, distinguish itself from sibling cross_source_email_connector, and the enum actions (which carry much of the real distinction) live in the schema rather than the description.

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 gives explicit downstream routing ('When the user asks for a visual... call chart_render') but never states when to use email_connector versus alternative email siblings like cross_source_email_connector. Usage is implied at the tool level with no exclusions, so this is minimum-viable guidance.

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