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

Annotations already declare read-only, idempotent, non-destructive, and closed-world, and the description is consistent with that ("opens nothing by itself"). Beyond annotations it discloses the non-obvious behavior that the payload is procedural guidance covering screens, buttons, and fields, and that execution requires a separate browser-tool workflow — information an agent cannot get from structured fields.

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 is front-loaded, but the description is padded with audience framing ("from ChatGPT, Claude or any AI agent") and a dangling sentence about Plausible's official API that trails off without telling the agent what to do with that fact. Trimming those would sharpen it without losing substance.

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 the essentials: what is returned (step-by-step instructions), that nothing is executed, and which tools carry out the action. It could add a hint about which browser tool typically starts the flow, but nothing critical for correct invocation is missing.

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 applies. No parameter-related misdirection is introduced.

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 ("Get top pages") but immediately reframes it: the tool returns step-by-step UI instructions rather than the page data itself. That reframing is essential because the name alone would mislead an agent into expecting analytics results; it is clear once read, though it takes a full sentence to correct the name's implication.

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 a clear next step — perform the task with cotlet_browser_* tools in the Plausible Cloud Browser — and mentions the official API is limited. It does not, however, distinguish this from sibling tools like plausible_get_site_stats, nor say when the API-based siblings are preferable over the instruction-plus-browser path.

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