pipedrive_activities_create

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 for a mutation tool, yet it never states side effects (record creation, webhook/notification triggers), auth or scope requirements, or error behavior. Its one behavioral claim — that the note is plain HTML passed without a CDATA wrapper — duplicates the note parameter's schema description rather than adding new context.

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?

Two short sentences with the core purpose front-loaded and no filler — effectively sized. The second sentence, however, restates schema content, so one of the two sentences does not fully earn its place.

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 13-parameter create tool with no annotations, no output schema, and roughly half the parameters undocumented, the description is far too thin to be complete. It gives no linkage semantics (which IDs link the activity to deals/persons/orgs/leads) and no post-creation behavior.

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 only 46%, so the description should compensate for the undocumented parameters (org_id, deal_id, lead_id, user_id, location, person_id, duration, etc.). Instead it addresses only 'note' and repeats what the schema already says, leaving most of the 13 parameters unexplained in either place.

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+resource ('Create a new activity') and names concrete instances (call, meeting, task), which cleanly separates it from siblings like activities_get, activities_update, activities_list, and activities_mark_done. It stops short of explicitly routing the agent between create vs. update/mark_done, so it is clear but not sibling-differentiating.

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?

There is no when-to-use guidance in the description, no prerequisites, and no mention of alternatives such as activities_update or activities_mark_done. The only routing hint ('call pipedrive_activity_types_list first') lives in the schema, not the description, so the description itself offers no contextual guidance.

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