pipedrive_update_task

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

Annotations are already informative (idempotent, not destructive). The description adds context about the Projects add-on and API beta status, and the milestone constraint beyond what annotations convey.

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 concise sentences, no redundancy. Each sentence adds necessary information: action, field requirements, naming hint, constraint, and context about add-on/beta.

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 12 parameters and no output schema, the description covers essential usage: required field, optional fields, naming consistency, and a key constraint. Lacks explanation of return value, but that is often implicit.

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 already covers all parameters with descriptions (100%). The description adds value by emphasizing the required field, recommending using same field names as GET, and adding a constraint on milestone/due_date.

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?

The description clearly states the tool updates an existing task, with a specific verb and resource. It distinguishes from create/get/list tasks among siblings.

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?

Explicitly states that only id is required and all others optional, and provides a constraint on milestone tasks needing due_date. However, it does not explicitly recommend alternatives or cases when not to use.

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