pipedrive_mail_thread_messages_list

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

No annotations provided, so description carries full burden. Only reveals that include_body gives full content, which is already in schema default. No disclosure of pagination, ordering, or read-only nature.

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?

Two sentences, no fluff. Front-loaded with purpose, then a concise usage hint. Every word earns its place.

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 no annotations, description provides basic purpose and parameter hint. However, it omits common list concerns like pagination, sorting, or response structure, which an agent might need to handle.

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 50% (thread_id described, include_body only type/default). Description adds 'Use include_body for full content', clarifying the boolean's effect beyond the schema. Helps agent understand the parameter's role.

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?

Description clearly states 'List messages within a mail thread' with a specific verb and resource. Among siblings, this distinguishes from pipedrive_mail_threads_list (lists threads) and pipedrive_mail_messages_get (gets a single message).

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?

Implies use when you need messages in a thread, but no explicit guidance on when to use alternatives (e.g., pipedrive_mail_messages_get) or when not to use this tool. The hint about include_body is useful but limited.

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