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

With no annotations provided, the description carries full burden. It clearly discloses that this is a read-only cache operation (no side effects), and describes the fallback behavior when location_code is omitted, plus notes that market fields are always present. This is substantial behavioral context beyond a simple read hint.

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 concise sentences, front-loaded with the tool's purpose and content list, followed by usage guidance. No filler or repetition. Every sentence adds value.

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?

The description lists the key components of the snapshot (authority, backlinks, organic keywords, top keywords, pages), which is essential since there is no output schema. It also explains market behavior. It doesn't mention error cases or pagination, but for a read-only snapshot this is adequate.

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 75% (3 of 4 params have descriptions). The description adds semantics for location_code by explaining the effect of omitting it, which the schema alone doesn't convey. It doesn't add detail for organization_id, but the schema already lacks a description there, so the description partially compensates for the gap.

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?

The description states a specific verb ('Snapshot') and resource ('analisi della concorrenza di un dominio'), and enumerates the exact content (authority, backlinks, organic keywords, top keywords, pages). It also distinguishes itself from the sibling run_domain_analysis by explicitly saying this is a cache read-only snapshot, so an agent can tell them apart 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?

It explicitly says when to use this tool ('Solo lettura della cache') and when to use the alternative ('per aggiornare usa run_domain_analysis'). It also clarifies the behavior without location_code (returns most recent analysis across markets), which guides selection when market-specific data isn't needed.

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