Load domain overview pages

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

Adds context the annotations do not carry: the API write scope requirement, the fact that a cache miss spends provider budget, that max_cost_cents=0 forces a cache-only attempt, and the snapshot_expired failure mode requiring a re-run of analysis. This is exactly the auth/budget/error-state disclosure an agent needs, and it is consistent with readOnlyHint=false and openWorldHint=true.

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 tight sentences with no filler, and the costly constraint (write scope, cost budget, cache-only escape hatch) is front-loaded. Minor deduction because the actual purpose statement trails the prerequisites rather than leading.

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 paid, seven-required-parameter paged read with no output schema, the description covers the two things that are easy to get wrong: authorization/cost preconditions and the snapshot_expired state. Pagination mechanics live in the schema, so the remaining gap is minor.

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 all nine parameters are already documented in the schema, including max_cost_cents's cache-only semantics. The description reinforces the max_cost_cents meaning but adds no new parameter-level detail, so the baseline 3 applies.

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 names a specific verb+resource: 'Loads one relevant-page result page for the current Domain Overview target.' That is concrete enough to distinguish it from load_domain_overview_keywords or load_domain_overview_history, but it never names those siblings explicitly, so differentiation is left to inference.

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 gives real preconditions ('Requires API write scope and an explicit max_cost_cents', 'Use zero for cache-only') and one routing hint ('snapshot_expired means analysis must run again first'), but it never states when to prefer this over analyze_domain_overview or estimate_domain_overview_cost. Usage is implied rather than spelled out.

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