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

Annotations cover the safety profile (readOnlyHint=false, non-idempotent, non-destructive, closed-world), and the description adds non-obvious behavior beyond them: the location is string-composed into the query as '<keyword> in <locationLabel>' and is explicitly NOT geocoded. That is a real implementation trait an agent would otherwise assume wrongly.

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?

Three compact sentences, front-loaded with the definition, followed by the composition rule and the next-step tools. No filler and no repetition of schema or annotation data.

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?

For a mutation config-creation tool with no output schema, the description covers what is created, how the location is interpreted, and which tools consume/read the result. The only minor gap is that it does not mention the created config's identifier being returned for later use.

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 adds genuine semantics for locationLabel: it explains how the value is composed into the query and warns that no geocoding occurs. It does not cover languageCode, which the schema handles.

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 and resource ('Creates a local pack rank check config') and immediately defines the resource's semantics: where businessName sits in Google's local pack for one keyword at one location. This clearly distinguishes it from siblings like create_local_rank_grid_config and create_rank_tracker.

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 routes the agent through the lifecycle: run checks with run_local_pack_rank_check and read them with get_local_pack_rank. It also flags cost context ('FREE: database only'). It does not state when NOT to use it (e.g. grid vs single-location), but the use case is unambiguous.

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