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

Annotations already declare readOnlyHint=false and openWorldHint=true, but the description adds substantial context beyond them: it spends credits, it notifies the customer as a side effect, max_credits aborts rather than overspends, confirmation behavior is configurable, and a Cotlet API key with app access is required. This is exactly the behavioral detail annotations cannot carry.

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 opening two sentences are duplicated nearly verbatim ('Spend credits to contact a lead... Bark notifies the customer' appears twice), wasting roughly a quarter of the text. The remaining content is front-loaded and useful, but the redundancy is a clear structural flaw.

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?

With no output schema, the description compensates by naming the returned fields (name, phone, email), and it covers cost, confirmation, side effects, and auth requirements. An agent has everything needed to invoke this correctly.

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 lead_id and max_credits are already documented. The description restates max_credits' fail-instead-of-buy behavior but adds no syntax, range, or format detail beyond the schema, so the 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 (contact a lead), the concrete outcome (returns name, phone, email), and the distinguishing cost model (spends credits). An agent can tell this apart from read-only siblings like bark_get_lead or bark_list_leads by the credit-spend semantics alone.

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?

Provides real usage context: confirmation is on by default, can be switched off per tool, and since it reaches other people the user must be confirmed before each call. It does not explicitly name alternative tools or say when not to use this one, so it falls short of a 5.

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