pipedrive_activities_delete

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

With no annotations provided, the description carries the burden and does disclose two useful behaviors: the explicit confirmation token gate and a dry-run preview mode. It omits what deletion actually destroys (linked notes, deal associations), permission requirements, and reversibility, which matters for an irreversible mutation.

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 with the core action front-loaded and zero filler. It is efficient, though the telegraphic style leaves the confirm/dry_run mentions as bare facts rather than integrated guidance.

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 tool with no annotations and no output schema, the description covers the confirmation guard and preview mode but is silent on consequences, permissions, and error behavior. It is minimally adequate rather than complete.

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 activity_id, confirm, dry_run and reason are all already documented with types, const, default and notes. The description only restates confirm and dry_run, adding no syntax or meaning beyond the schema; 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 an activity") so the agent immediately knows the operation. It does not, however, distinguish itself from nearby siblings such as pipedrive_activities_mark_done or pipedrive_activities_update, which an agent could confuse with deletion.

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 implies a guarded destructive workflow (must pass confirm: "DELETE", dry_run available) but never says when to prefer this over mark_done/update or when deletion is appropriate. Usage is inferable from the operation name rather than stated.

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