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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral information beyond them: 'opens nothing by itself' confirms the tool performs no navigation or mutation, and the note that Bark has no public API for professionals explains why the browser path exists at all. Minor redundancy with the annotations keeps this from a 5.

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 core behavior and the follow-up instruction are front-loaded in the first two clauses, which is good structure. The final sentence about Bark's missing public API is justified context but reads as a slightly clipped fragment, and the whole description is one dense run-on that could be split for clarity.

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 parameters, no output schema and full annotation coverage, the description supplies what an agent needs: what comes back (screens, buttons, fields), that nothing is opened, and which tool family to use next. The only remaining ambiguity is how this guide tool relates to the sibling bark_list_new_leads and bark_list_my_responses tools.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter detail is missing because no parameters exist.

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?

The description states a specific resource (lead details in the user's own Bark account) and then clarifies the actual output: 'Returns how to do it in Bark step by step (screens, buttons, fields).' That disclosure is valuable because the name suggests data retrieval while the tool really returns instructions. It does not, however, differentiate itself from siblings like bark_list_new_leads or bark_list_my_responses, so an agent cannot tell from the description alone which lead-related tool to pick.

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?

It gives clear workflow context: call this first to get the step-by-step procedure, then execute it with the cotlet_browser_* tools in the user's Bark Cloud Browser. That sequencing is exactly what an agent needs to act correctly. The gap is the absence of explicit exclusions or a comparison against the other bark_* guide tools.

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