deals_list_mail_messages

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

Discloses caching (5 minutes), sorting (newest first), and that both sent and received emails are included. No annotations are provided, so the description carries full burden and adds valuable behavioral context.

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?

Concise with a clear main sentence followed by bullet points for tips and use cases. Every sentence is informative and front-loaded with purpose, making it efficient for quick comprehension.

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?

Given no output schema, the description adequately explains return content (all emails, sorted, cached). It covers pagination and typical use cases, which is sufficient for a list tool with three parameters.

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 100%, and the description enhances parameters with practical examples (e.g., { 'id': 123 } and { 'id': 123, 'start': 0, 'limit': 50 }) and explains pagination, adding value beyond schema definitions.

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 clearly states 'List mail messages associated with a deal' with a specific verb and resource, distinguishing it from sibling tools like persons_list_mail_messages and organizations_list_mail_messages.

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?

Provides workflow tips and common use cases with example JSON, including pagination guidance. Does not explicitly exclude alternatives but gives enough context for appropriate usage.

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