organizations_list_mail_messages

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions pagination support and the types of messages returned but omits details like sorting order, permission requirements, rate limits, or default behavior. This leaves significant gaps for an agent to safely invoke the tool.

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 structured with a summary sentence followed by bullet points, which aids readability. However, it is somewhat verbose with multiple use-case bullets that add limited value relative to length. Could be more concise.

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 the absence of an output schema and annotations, the description provides a reasonable overview of what the tool returns and its use cases. However, it lacks details on prerequisites, error handling, and specific behavioral expectations, leaving the agent with incomplete context for robust 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?

All three parameters are described in the input schema (100% coverage). The description adds no additional meaning beyond the schema, such as format constraints or interaction effects. Baseline score of 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 clearly states the tool lists mail messages associated with an organization and enumerates the types of data returned. However, it does not distinguish this tool from similar siblings like 'persons_list_mail_messages' or 'deals_list_mail_messages', which are likely analogous.

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 lists several use cases (e.g., reviewing communication history, understanding customer interactions) but does not explicitly state when to use this tool versus alternatives. It implies usage for organization-level email history but lacks when-not-to-use guidance.

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