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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false). The description adds context the annotations cannot: the call is database-only and FREE, i.e. it persists a config without triggering a paid rank run, and centerLabel is effectively mandatory in substance, not just by schema. The non-idempotent behaviour (what happens if a duplicate config is created) is left unstated.

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 core definition, then the centerLabel constraint, then the workflow and cost note. Every sentence carries information, though the rhetorical clause 'a heatmap with no stated centre is a claim about nowhere' is slightly ornate for a tool definition.

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?

Covers creation semantics, the required labelling constraint, the follow-up tools for running and reading, and the cost model — enough for an agent to call it correctly without an output schema. It stops short of documenting duplicate-config behaviour or what the created config ID looks like for subsequent run/get calls.

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 already 100%, so the baseline is 3. The description goes beyond it by explaining the semantics of the grid itself (3x3 points around a centre, organic-only rank, one keyword/domain per point) and by giving centerLabel a stated requirement plus rationale rather than only an example value.

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+resource ('Creates a geo-grid rank-tracking config') and immediately defines the object: a 3x3 grid around a centre coordinate checking ORGANIC rank for one keyword/domain. This is precise enough to separate it from the sibling run_local_rank_grid and get_local_rank_grid, which it names as the lifecycle partners.

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 tells the agent what to do after creation ('Run it with run_local_rank_grid and read it with get_local_rank_grid'), which routes the agent into the correct workflow. It does not, however, address the closest alternative (create_local_pack_rank_config) or state when a grid config is preferable to other rank-tracking setups.

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