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

Annotations only declare destructiveHint=true, so the bar is lower, and the description does add the underlying REST operation (POST /api/v2/activities) plus the required-field constraint. It discloses nothing about permissions, side effects on linked entities, or whether the created record is returned, so it is only marginally additive.

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 with the core purpose front-loaded and no filler. The endpoint sentence is the only borderline element, but it is compact and gives an agent a useful anchor to the API surface.

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?

With 11 parameters and no output schema, the description covers the call adequately but omits what the call returns (e.g., the new activity id needed for follow-up operations). It is sufficient to invoke the tool but leaves a gap an agent creating a linked workflow would notice.

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% across all 11 parameters, so the schema already carries the semantics. The description lightly groups parameters (linkage fields, type/date/time) and restates that subject is required, which is duplicative rather than additive. 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 ('Create a new activity (task/event)') and clarifies the ambiguity of 'activity' with the parenthetical, which separates it from siblings like pipedrive_add_note or pipedrive_create_deal. It does not explicitly name a sibling to contrast against, 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 line 'link it to a deal/person/org and set type/date/time as needed' implies when the linking fields matter, but gives no guidance on when to create an activity versus adding a note or creating a related entity. Usage is inferable but not stated.

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