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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds value beyond them: it discloses what is actually returned (screens, buttons, fields) and explicitly states the tool performs no action itself. That is meaningful disclosure of output shape and side-effect absence for a zero-parameter tool.

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 critical fact — that this returns instructions rather than keyword data — is deferred to the second sentence after a misleading opener. The final sentence about the official API and MCP server is repetitive and carries a check date that adds little for invocation decisions, so it does not fully earn 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?

With no parameters and no output schema, the description carries the burden of describing the return value, and it does so reasonably ('step by step (screens, buttons, fields)') while also naming the follow-up tools. It does not clarify whether the procedure covers all keywords or a filtered subset, which is a minor remaining gap for a zero-input tool.

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; the baseline for zero-parameter tools applies. The description correctly does not invent inputs and instead frames the tool as a guide generator.

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 second sentence makes the real behavior explicit: it returns a step-by-step procedure for listing keywords and ranks in AccuRanker and 'opens nothing by itself'. That is a clear verb+resource, though the headline phrasing 'List keywords and ranks' reads like a data-returning tool and no sibling (e.g. accuranker_get_keyword_rank_history) is named to differentiate 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?

It explains the workflow role ('then do it with the cotlet_browser_* tools in the user's AccuRanker Cloud Browser'), which is useful sequencing guidance. However, it only notes in passing that an official API and MCP server exist without saying when to prefer this UI-procedure route over those alternatives, so selection guidance is implied rather than stated.

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