pipedrive_note_comments_delete

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

With no annotations, the description carries the full burden. It usefully discloses that this is a guarded destructive operation (confirm must equal "DELETE") and that a dry_run preview exists, which is real behavioral value. However, it says nothing about permanence, required permissions, or what happens if the comment_id is invalid.

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 sentences, front-loaded with the action, then the safety gate, then the preview option. Tight and readable, though the dry_run sentence largely duplicates the schema's own description.

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?

There is no output schema and no annotations, so the description must carry the full context. It covers the critical safety mechanics (confirm, dry_run) but omits irreversibility, error behavior, and return shape, leaving meaningful gaps for a destructive 5-parameter tool.

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%, so the schema already documents all five parameters including the confirm const and dry_run semantics. The description merely restates confirm and dry_run and adds nothing about note_id, comment_id, or reason, so 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?

States a specific verb and resource ("Delete a comment from a note") that is unambiguously distinct from the sibling create/update/list comment tools. It does not explicitly name those siblings, but the operation is clear enough that no agent would confuse them.

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 when-to-use context, no prerequisites, and no mention of alternatives such as update vs delete or the parent note tool. The only conditional guidance is the confirm requirement, which is a safety gate rather than usage guidance.

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