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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely non-redundant behavior: it reports ORGANIC rank only and NEVER local-pack position because the backend does not parse a local pack. That caveat prevents a real misinterpretation of the returned data, and the null meaning for the reverse-geocoded place name is also disclosed.

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?

Front-loaded with the read-only scope and the two behavioral branches, then the CRM caveat, then the related-tool pointers. Every sentence carries load; there is no filler or restatement of the title.

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 carries the return-value burden and does describe the per-point fields and the null convention. It stops short of the full response shape (e.g. list-mode payload, volume of points, pagination), but it is sufficient to call the tool 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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining what the configId branch actually yields (latest run plus per-point position/url/place-name results). It does not add syntax or format detail for projectId, but the added return semantics for configId justify a step above baseline.

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 precise verb+resource: reading geo-grid rank-tracking configs and their latest run. It spells out the two distinct modes (with configId = single config's latest run + per-point results; without = list all configs), and explicitly names the sibling tools used to create a config and trigger a run, so an agent can place it 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?

It clearly states the calling context for both branches and explicitly routes to create_local_rank_grid_config and run_local_rank_grid for the write/trigger paths. It does not, however, say when to prefer this over nearby siblings like get_local_pack_rank or get_rank_config_trend, so the alternative-selection guidance is incomplete.

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