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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful substance beyond that, notably the ethical constraint 'Mirror the structure and coverage, never the words,' but says nothing about runtime cost, latency, or whether results are cached across calls.

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 tool's substance is front-loaded and the closing two-word imperative is excellent, but the core sentence runs nearly a hundred words with nested parentheticals, forcing the agent to parse a list inside a clause instead of reading a structured breakdown.

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 burden and does so: it enumerates the evidence gathered (headings, length, sections covered, form and phone placement, schema, FAQ, reviews), the synthesis (shared pattern, client gap), and the deliverable (outline). Nothing needed to call or interpret it is missing.

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 still adds meaning by framing 'area' as the client's locality with a concrete analogy (Fresno for a Snohomish County shed builder) and by explaining that 'target_url' comes from the keyword map and that markets are for when local winners are weak.

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 ('study') and a precisely bounded resource: the pages Google Maps ranks for a service in the client's area, what each winning page covers, and how the client's page compares. The output artifacts (pattern, gap, outline) make it distinguishable from siblings like keyword_strategy or landing_evidence without opening schemas.

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 opening clause 'before building or reworking one' gives a clear trigger condition, and the 'also_markets' guidance explains the fallback when local winners are weak. It does not name a competing tool to use instead, so it stops short of explicit alternative routing.

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