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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description usefully reinforces this with "opens nothing by itself," confirming it is a non-acting guidance tool. Beyond that it adds no operational traits such as rate limits, auth requirements, or what happens if the Cloud Browser is unavailable.

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 mechanic is front-loaded in the first sentence and the follow-up action is stated before the supporting rationale. The final sentence about the official API is a slightly awkward fragment with a parenthetical date, but it justifies the browser-based approach and earns its place.

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 zero-parameter, no-output-schema tool, the description covers what matters: what it returns (screens, buttons, fields) and what the agent must do next. The only ambiguity is how the buyer is scoped, which neither the description nor the schema resolves.

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 no parameter meaning to convey and the baseline applies. The description does not needlessly invent parameter talk. One residual gap is that it never explains how the target buyer is identified given the empty schema, which an agent may wonder about.

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 verb and resource ("Contact buyer in the user's own Bark account") and immediately clarifies the actual mechanic: it returns step-by-step instructions rather than performing the contact. That distinguishes it from the cotlet_browser_* siblings that perform the interaction, though it does not name a specific sibling tool it competes with.

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 usage context: call this to learn the Bark flow, then execute it with cotlet_browser_* tools in the user's Bark Cloud Browser. The rationale (no public API for professionals) explains why this path is required. What's missing is any explicit precondition such as which lead/buyer context must already be established.

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