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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds real value beyond them: the customer is not notified, no confirmation is required, the note can be overwritten with another call, and an API key/sign-in is needed. It stops short of describing the return value or exact auth scoping.

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?

Front-loaded with the key privacy point, but the opening line and the second sentence redundantly restate the same idea ('Private note on a contacted lead' / 'Adds a private note to a contacted lead'). The 'does not ask for your OK' phrasing is informal and costs space without adding precision.

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 two-parameter write tool with annotations and no output schema, the description covers purpose, privacy semantics, mutability, and auth requirements. It is nearly complete; only the response/confirmation behavior and explicit routing to alternatives are absent.

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%, so both parameters (note, lead_id) are already documented in the schema, including the lead_id source (list_leads or list_responses). The description adds no param-level syntax or format detail beyond what the schema provides, so baseline 3 applies.

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 ('Adds a private note to a contacted lead') plus the object type, and the privacy framing distinguishes it from customer-facing siblings like bark_send_message. However, no sibling tool is named explicitly, so the differentiation 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?

Usage is implied ('to track the job') but there is no explicit when-to-use/when-not guidance and no alternatives named. An agent must infer that this is for internal tracking rather than customer communication.

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