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

Annotations already declare readOnly/idempotent/non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior in flagging that calls spend API units ('[read · spend]', 'Consumes API units') — a cost signal not present in structured fields. It doesn't mention rate limits or response shape, keeping it below a 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?

A single tightly packed sentence with the cost/read tag front-loaded. Every clause adds information; nothing is padded. The compressed bracket notation is slightly cryptic but efficient.

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?

No output schema exists, so the description should ideally sketch what 'rank' and 'organic keywords' return (top-N keywords? limit? totals?). With 4 optional params and 0% schema coverage, the definition is adequate for invocation but leaves the result-shape unknown.

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?

Schema coverage is 0%, so the description carries real weight. It documents the 'database' parameter with examples and a default ('us, tr, de...; default us') and explains the two account-identifier parameters. The 'domain' parameter and the rank/keywords payload semantics are not elaborated, so compensation is partial.

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?

Names the resource precisely (domain overview rank + organic keywords for a domain) and scopes it to a regional database. An agent can tell it apart from semrush_backlinks and semrush_units, though the verb is implied rather than stated (the '[read · spend]' tag carries 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?

Gives useful operational context — database defaults to us, calls consume API units, and account can be identified by id or uuid. It stops short of saying when to prefer this over semrush_backlinks or semrush_units, so alternatives are left implicit.

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