pipedrive_notes_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 flags the confirmation gate, but that is already stated in the schema's const and dry_run descriptions, and it omits the essentials for a destructive operation: irreversibility, permission requirements, and side effects such as what happens to attached note comments.

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 terse sentences, front-loaded with the verb and resource, then the safety requirements. Every sentence carries information and there is no filler.

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 destructive mutation with zero annotations and no output schema, the description is too thin. It never states that deletion is permanent, whether a dry_run preview has any cost, or that the reason field is accepted, leaving the agent without the context needed to call this safely.

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 note_id, confirm, reason, and dry_run are all documented in the schema itself. The description repeats confirm and dry_run without adding format, constraint, or edge-case meaning, 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?

States a specific verb and resource ('Delete a note'), which an agent can distinguish from pipedrive_notes_get/update/list by name. It does not explicitly name or contrast with a sibling, so it falls short of a 5.

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 gives procedural requirements (confirm must be "DELETE", dry_run available) but no when-to-use guidance, no prerequisites, and no mention of alternatives for removing note content. Nothing tells the agent under what circumstances deletion is appropriate.

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