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

Annotations already establish that this is a safe read-only, non-destructive, closed-world operation. The description adds useful behavioral context beyond the annotations: it returns both sent emails and received replies, caps results at 50 messages, and supports pagination via skip.

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, front-loaded sentence with no wasted wording. It states the core action, scope, result limit, and pagination mechanism efficiently.

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 rich structured metadata (100% schema coverage, annotations, and an output schema), the description covers the essential purpose, result limit, and pagination. It is complete enough to call correctly, though it could be stronger with explicit alternative-tool routing.

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%, so the input schema already documents all three parameters including ids, skip, and workspace_id. The description reinforces pagination via skip but does not add parameter meaning beyond the schema, so the baseline 3 is appropriate.

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 uses a specific verb and resource: retrieve sent emails and received replies across multiple senders. It clearly implies a bulk/multi-sender scope that differs from the singular fetch_sender_messages sibling, but it does not explicitly name or route to that alternative.

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 only implied by 'Bulk Fetch' and 'across multiple senders.' The description mentions the max 50 limit and skip-based pagination, but it does not explicitly say when to use this tool instead of fetch_sender_messages or other message-fetching siblings.

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