pipedrive_mail_threads_delete

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

No annotations are provided, so the description carries the full behavioral burden. It surfaces the destructive-confirmation gate and dry_run preview, which is useful, but both are already spelled out in the schema descriptions, so it adds little beyond structured data. It never says deletion is irreversible or whether thread messages cascade-delete.

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?

Three short clauses, front-loaded with the action, then the safety requirement, then the optional mode. No wasted words.

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?

For a mutation tool with no annotations and no output schema, the description covers the confirmation mechanism but omits consequences (irreversibility, cascade to messages) and what dry_run output looks like. Minimum viable but with clear gaps.

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%: thread_id, confirm (const DELETE), dry_run, and reason are all documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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?

Clear specific verb+resource: 'Delete a mail thread.' An agent can immediately tell it apart from pipedrive_mail_threads_get, _list, _update, and _mail_thread_messages_list. It does not explicitly name sibling alternatives, but the resource is unambiguous.

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?

States the operational precondition (confirm: "DELETE") and the dry_run option, which implies usage, but gives no guidance on when to delete vs. archive/update a thread or any consequences/exclusions. Adequate but leaves alternatives unaddressed.

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