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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description usefully reinforces that with 'opens nothing by itself'. It also discloses the shape of the return value (screens, buttons, fields), which annotations cannot express. The trailing note that AccuRanker has an official API and MCP server is ambiguous — it is unclear whether it is a caveat, a preference, or trivia — which keeps this below 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 disclosure — returns instructions, opens nothing, execute via browser tools — is front-loaded and clear. But 'from ChatGPT, Claude or any AI agent' is filler, and the closing sentence about the official API/MCP server with a checked date adds noise without a stated consequence.

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 zero parameters and no output schema, the description carries the burden of explaining the return value, and it does so concretely (step-by-step screens, buttons, fields) plus the crucial no-side-effect guarantee. What remains unclear is how the returned steps relate to the specific cotlet_browser_* calls the agent should make next.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the text misleads about inputs.

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 keyword rank history in the user's AccuRanker account) and then corrects the likely misreading of the name by saying it returns a step-by-step how-to rather than the data itself. That clarification is what lets an agent distinguish this from data-returning siblings such as accuranker_list_keywords_and_ranks, though it never names such a sibling explicitly.

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 usable workflow: call this to obtain the procedure, then perform it with cotlet_browser_* tools in the AccuRanker Cloud Browser. There is no explicit when-not guidance and no routing between this and the API-based AccuRanker siblings, so the agent must infer the choice.

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