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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world; the description adds genuinely new behavioral facts — that it emits instructions (screens, buttons, fields) and performs no browser action — which is exactly what an agent needs to avoid expecting a navigation side effect. No return-shape detail is given, but the tool is a static guide so the remaining risk is low.

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 operational content is front-loaded and clear, but 'from ChatGPT, Claude or any AI agent' is promotional filler, and the parenthetical API-v2 survey (with a date) is tangential justification rather than actionable instruction. The useful constraints could be stated in half the words.

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 parameterless, read-only guide tool with full annotation coverage, the description covers what it returns, what it does not do, and which tools to chain next. There is no output schema to explain, and an agent has everything needed to invoke it and act on the result.

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 the baseline is 4. The description correctly implies no arguments are needed and frames the output as a fixed procedural guide, leaving nothing for the schema to cover.

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 and immediately clarifies the surprising part: it returns step-by-step instructions rather than analytics data, and does not navigate anywhere itself. This disambiguates it from dribbble_list_shots and the cotlet_browser_* siblings, though the name 'Get Pro analytics' still reads like a data fetch until the second sentence corrects it.

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?

Explicitly states the follow-up path: use cotlet_browser_* tools in the user's Dribbble Cloud Browser after reading the guide, and notes that the tool 'opens nothing by itself.' The official API note also implies why a browser-based guide is needed. It stops short of stating when to prefer this over cotlet_app_guide for Dribbble specifically.

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