pipedrive_notes_create

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

With no annotations, the description carries the full behavioral burden. It does disclose a genuine input-handling trait (HTML passed directly, no CDATA wrapper), but says nothing about permissions, whether undirected notes are allowed, or what is returned on success.

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, front-loaded with the purpose before the format caveat. Efficient, though the second sentence partially duplicates what the content_html schema property already says.

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?

An eight-parameter mutation tool with 63% schema coverage, no annotations, and no output schema needs more context than two sentences provide. The pinned_* flags and the implicit requirement of at least one attach target are left entirely undocumented.

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 63%, so the schema already documents most parameters, including an extensive content_html description. The description's CDATA caveat mostly restates that schema text, and it adds nothing about the three pinned_* flags or the attach-target semantics.

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 (Create) and resource (a note) plus the four entity types it can attach to, which is enough for an agent to distinguish it from pipedrive_notes_list, pipedrive_notes_update, and pipedrive_note_comments_create. It does not explicitly contrast itself with those siblings, but the scope is unambiguous.

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?

No guidance on when to create a note versus a note comment versus an activity, and no prerequisites are stated. Critically, the description never says that at least one of deal_id/person_id/org_id/lead_id is needed for the note to be useful, even though none of them appear in the required list.

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