pipedrive_notes_create

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

The description reveals that the note content is in HTML format and that the note can be attached to multiple entity types. However, with no annotations provided, it lacks details on authentication, rate limits, success/failure behavior, or side effects. The transparency is average but not thorough.

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?

The description is extremely concise, consisting of two sentences with no filler. It front-loads the action and key resource. Every sentence serves a purpose.

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 the high parameter count (8) and lack of output schema, the description is insufficient. It does not explain whether multiple entities can be specified at once, how pinned flags work, or what the response contains (e.g., created note details). Sibling tools like pipedrive_notes_get exist, but no cross-reference is made.

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 coverage is only 13% (only content_html described). The description adds minimal value: it mentions 'attached to a deal, person, org, or lead' which hints at the ID parameters, but does not explain their usage, constraints, or the meaning of pinned flags. Given low schema coverage, the description should compensate but does not.

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 action (create a note) and specifies the resources it can be attached to (deal, person, org, or lead). It also mentions that content is HTML, which adds specificity. This effectively distinguishes it from sibling tools like pipedrive_notes_list, update, delete, etc.

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 usage for attaching notes to various entities but does not provide explicit guidance on when to use this tool versus alternatives (e.g., pipedrive_notes_update or pipedrive_activities_create). No exclusion criteria or prerequisites are mentioned.

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