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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower; the description still adds return shape, the fact that no rank check is performed, and a cost signal ('FREE: database only'). It omits any note on error or pagination edge behavior, keeping it just short of 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?

Two dense sentences, front-loaded with the scope constraint, followed by the return shape, negative capability statement, id semantics and cost. No filler; every clause carries information.

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 output schema, the description compensates by naming the top-level return fields and per-row fields, and clarifies what is not returned. For a paginated read-only list tool this is complete enough to call correctly.

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 description coverage is 100%, so the baseline is 3; the description goes further by explaining the semantic role of the returned row 'id' (the tracking-keyword ID consumed by remove_rank_tracking_keywords, update_rank_keyword_tag and set_rank_keyword_target_url), which the schema does not convey.

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 ('Lists'), a tightly scoped resource ('keywords tracked by ONE rank tracker'), and explicitly disambiguates from the sibling get_rank_tracker by noting it returns no positions. An agent can distinguish this from the ~150 siblings without opening the schema.

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 states the when-not ('returns NO positions and runs no check') and names the alternative tool to use instead ('read positions with get_rank_tracker'), plus identifies the three consumer tools that take the returned id. Routing guidance is unambiguous.

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