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

Adds real context beyond the annotations: the tool 'opens nothing by itself' and returns only a procedural guide, consistent with readOnlyHint=true. The note that Google's official API covers only part of the web interface explains why browser automation is needed. However, it never says what metrics, date ranges, or filtering the resulting guide covers, which is what an agent actually needs to plan the follow-up calls.

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 operative information (returns instructions, execute via cotlet_browser_* tools) is present but buried after promotional phrasing ('from ChatGPT, Claude or any AI agent') and repetitive restatement of 'Google Search Console'. The trailing API-coverage sentence is background justification rather than actionable guidance and could be cut or moved.

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 tool with no output schema, the description should fully explain what the returned guide contains and how to continue. It covers the continuation path well but leaves the shape of the output and the available performance dimensions (clicks, impressions, CTR, position, date range) unspecified, forcing the agent to discover them through browser steps.

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 schema is trivially complete and there is nothing for the description to disambiguate. Baseline 4 applies; nothing in the description contradicts or misuses parameters.

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 and resource ('Get performance stats in ... Google Search Console') and scopes it to the user's own account. It then clarifies the actual deliverable is a step-by-step how-to rather than the raw data, which is honest but slightly at odds with the name and makes the tool's output identity ambiguous. It does not explicitly distinguish itself from siblings like google_search_console_get_links_report.

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 routes the agent: this tool returns the guide, then execute the steps with cotlet_browser_* tools in the user's GSC Cloud Browser. That is a concrete when-to-use and which-alternative path. It stops short of stating when not to use it (e.g., if the user only wants link data, use get_links_report).

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