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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral fact beyond that — the 50-message result cap and the skip-based pagination pattern — but says nothing about ordering, completeness of the sent/replies union, or truncation behavior when the cap is hit.

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?

A single tight sentence with the pagination constraint placed where an agent will see it. The leading restatement of the title ('Fetch Sender Messages -') is redundant, which keeps it just short of a 5.

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?

An output schema exists so return values need no explanation, and the schema fully documents the inputs. What is missing for a tool with a very similar sibling is any disambiguation from fetch_multiple_sender_messages, which is the main decision an agent has to make here.

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 all three parameters (id, skip, workspace_id) are documented in the schema, so the baseline of 3 applies. The description only restates the pagination role of skip and adds nothing about defaults or the workspace fallback that the schema does not already convey.

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 and resource with scope: retrieves both sent emails and received replies for a single sender. This is clear, but it does not distinguish the tool from the sibling fetch_multiple_sender_messages, leaving the singular-vs-multiple distinction to inference.

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 only usage guidance is operational: results are capped at 50 and 'use skip for pagination'. There is no statement of when to choose this over fetch_multiple_sender_messages or other message-reading siblings like get_thread_messages or get_lead_messages, so the usage context is only implied.

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