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

Annotations already declare readOnlyHint/openWorldHint, but the description adds real behavioral value: that listing is free of credit cost, sends no customer notification, and that each item carries credit cost and signals like 'urgent'. Mentions the Cotlet API key requirement with app-level access. No return format or pagination detail, but the added cost/notification context is substantive.

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 and reasonably tight, but the opening clause 'Leads matched to your services and locations, newest first' is restated almost verbatim in the second sentence, which is wasted space. The free-read guidance is well placed.

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?

No output schema, but the description sketches the return contents (credit cost, urgent-style signals) and the key requirement, so an agent knows what it gets and what auth it needs. Only the exact response shape and pagination semantics are left unspecified.

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 all six parameters are already well-documented, including enum values and defaults. The description only echoes the default sort ('newest first') and adds nothing about filter syntax beyond the schema. 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 (list) and resource (leads), plus the scoping (matched to your services and locations) and ordering (newest first). This is enough to distinguish it from bark_get_lead, though no sibling is named explicitly.

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 line 'Reading a list spends no credits and notifies no customer' gives a reason to use it, but there is no explicit when-to-use guidance against alternatives like bark_get_lead or bark_list_responses. Usage is implied rather than framed.

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