pipedrive_deal_mail_messages_list

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

The description does not disclose that the tool is read-only, nor does it explain pagination behavior (cursor and limit parameters) or response format. With no annotations provided, the description fails to convey important behavioral traits.

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?

At 8 words, it is very concise but arguably too brief. It sacrifices clarity and detail for brevity. A slightly longer description could improve understanding without losing conciseness.

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 and low parameter coverage, the description should explain what the agent will receive (list of mail messages) and how pagination works. It does not, leaving the agent with insufficient context to invoke the tool correctly.

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?

The schema has 33% description coverage (only deal_id is described). The description adds no extra meaning to the parameters – cursor and limit are left for the agent to infer. The tool would benefit from clarifying that cursor is a pagination token and limit caps the result count.

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 action (List) and resource (mail messages) scoped to a deal. However, it does not distinguish from similar sibling tools like pipedrive_mail_thread_messages_list or pipedrive_person_mail_messages_list, which could cause confusion.

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?

No guidance on when to use this tool versus alternatives. It does not mention any prerequisites or conditions for usage. The description is too minimal to provide context for tool selection.

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