pipedrive_note_comments_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, yet it only discloses the content_html format nuance (no CDATA wrapper). It says nothing about required permissions, what happens on an invalid note_id, whether comments are editable after creation, or rate limits — significant gaps for a mutation tool.

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 tight sentences with the action front-loaded and the format caveat second. No filler or repetition, though it is on the terse side given what a mutation tool ought to convey.

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 create tool with no annotations and no output schema, the description is too thin. It omits permission requirements, the expected success/error behavior, and any reference to the related update/delete/list sibling tools that an agent would need to reason about the operation.

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%, with both note_id and content_html well documented, including sanitization and CDATA guidance. The description's note about plain HTML without a CDATA wrapper echoes what the schema already states, so it adds little beyond the baseline.

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: 'Add a comment to a note.' An agent can immediately tell this is the create operation for note comments. It doesn't explicitly contrast with the sibling update/delete/list comment tools, but the name plus verb make the distinction clear without opening the schema.

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 gives no when-to-use guidance, no prerequisites, and never names the alternative comment tools (update, delete, list). The only routing signal is the tool name itself, so the agent must infer everything about appropriate usage.

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