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

Beyond readOnlyHint/destructiveHint/openWorldHint, it discloses security-relevant behavior that annotations cannot express: the DataForSEO login is masked and the password is never returned. It also explains the two account modes (own connected account vs. CrunchJunkie-managed with account.source = "managed") and that costs are historical for the last 28 days, which is real context for mutation-adjacent decisions.

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 intent is front-loaded in the opening clause, but the whole description is one long run-on sentence with a nested parenthetical and a comma-chained list of eight or so facets. Every element is informative, yet the lack of sentence breaks or structure makes it harder to scan than it needs to be.

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?

There is no output schema, so the description carries the return-value burden, and it does so well: it enumerates the account/connection state, tracked domains, schedule and timezone, engines and devices with keyword counts, per-run and monthly cost ceilings, and realized 28-day spend. Only the exact shape/field names of the response are unspecified.

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?

There is a single parameter and schema coverage is 100%; the schema already documents clientId and points at list_clients. The description adds no additional syntax or constraint details beyond that, so the baseline 3 applies.

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 conveys a specific resource — the rank-tracking setup for one client — and enumerates its facets (account connection mode, tracked domains, weekly schedule, engines/devices, cost ceilings, actual 28-day spend). It is clearly distinguishable from siblings like set_rank_schedule or refresh_rankings because it is described as a read of current configuration rather than a change, though it frames this as a noun phrase ('How rank tracking is set up') rather than an explicit verb like 'return'.

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?

The final clause, 'It shows the cost ceiling before keywords are added or a refresh is started,' implies a pre-mutation check use case, which is genuine guidance. However, it never names the alternatives (add_rank_keywords, refresh_rankings, set_rank_schedule) or states when-not to use it, so the agent must infer the routing from sibling names.

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