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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond them: the network scope (public HTTP/HTTPS only) and the explicit failure boundaries (no login/CAPTCHA/paywall bypass), plus what the response contains. Rate limits, timeouts and error behavior are not disclosed.

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 sentences, each doing distinct work: what it extracts, what it will not do, and what it returns and feeds. The key scope constraint is front-loaded and there is no filler.

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 an output schema present, return values need not be enumerated and annotations cover the safety profile, so the description is close to sufficient. It stops short of stating what happens when a URL is non-public or unfetchable, which would matter for an openWorld, network-dependent tool.

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 sourceUrl and locale are already fully documented in the schema. The description restates the public-URL constraint but adds no syntax or format detail (e.g. locale behavior, URL normalization) beyond the structured fields, 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?

States a specific verb (fetch/import) and resource (public website URL) plus the concrete payload it produces (business name, description, contact links, suggested page blocks). It also names the downstream consumer, page_create_from_brief, so the agent can place it in the workflow without opening a schema.

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?

Gives explicit boundaries: only public HTTP/HTTPS pages, and it does not bypass login, CAPTCHA, or paywalls. It implies when to use it by naming page_create_from_brief as the follow-on, but does not name an alternative tool for pages behind auth or otherwise inaccessible sources.

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