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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses meaningful behavior: the customer is notified as an external side effect, the amount is denominated in Bark currency, and it requires a Cotlet API key with app access. It could still say more about irreversibility or failure behavior, but it adds real context the annotations don't 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 description repeats itself almost verbatim: 'Send a quote on a contacted lead. Bark notifies the customer.' appears twice. That is wasted space, though the remaining content is short. Front-loading is fine but the duplication 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?

For a mutation tool with no output schema, it covers the essentials: action, external side effect, currency, and auth. The confirmation guidance is muddled, leaving the agent unsure whether/how it must confirm before sending. Adequate but with a clear gap in the confirmation semantics.

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 the three parameters are already fully documented in the schema. The description's only parameter-relevant statement, 'The amount is in your Bark currency,' duplicates the schema wording verbatim, adding no new meaning. Baseline 3 is appropriate.

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 (send a quote/estimate on a lead) and scopes it to an already-contacted lead, which implicitly separates it from bark_contact_lead and bark_send_message. It does not name an explicit sibling alternative, so it falls short of a 5, but an agent can tell what it does.

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 'lead you already contacted' scope implies when this applies, and the confirmation notes give some operating context. However, the line 'By default you confirm each call; you can switch that off for this tool' is confusing and never names alternatives or an explicit when-not-to-use condition. Usage is implied rather than clearly stated.

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