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

Annotations only supply destructiveHint=true, so the description carries most of the burden. It adds real context by disclosing the API generation ('Uses v1, v2 has no notes endpoint') and the REST endpoint, which explains why the call behaves as it does. It says nothing about permissions, failure modes, or what mutating a linked entity implies, and does not reconcile the destructiveHint=true annotation with an additive 'add' operation.

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 sentences, zero filler, with the core purpose and linking constraint front-loaded before the implementation notes. Every sentence carries either a constraint or an implementation fact an agent needs.

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 simple single-object create tool with no output schema and thin annotations, the description covers required input, the link constraint, and the API version quirk. Its only meaningful gap is the return shape (e.g. the created note id), which nothing else in the definition supplies.

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 100% so the baseline is 3, but the description adds semantics the schema does not encode: only `content` is required and at least one link id must be supplied, a constraint invisible in the schema's required list. It also confirms `content` accepts HTML or plain text, matching but reinforcing the schema.

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 note') plus the binding constraint that it must link to at least one deal/person/organization/lead, which genuinely narrows what the call means. It does not name the counterpart sibling (pipedrive_list_notes) or distinguish itself from pipedrive_create_activity, so sibling separation is only implicit.

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?

'linked to at least one of a deal/person/organization/lead' functions as an eligibility rule for when the tool applies, and the required `content` is called out. However there is no explicit when-to-use/when-not guidance, no mention of the sibling list_notes or of other creation tools (create_activity, create_deal), leaving the agent to infer routing.

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