Extract presence signals

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile and network reach are covered. The description adds the extraction scope but says nothing about failure modes (unreachable site, paywalled content), timeouts, or whether it renders JavaScript — relevant for an open-world web fetch.

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?

One tight sentence front-loads the verb and resource, then lists outputs, then names the consumer. 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 no output schema, the description must carry the return shape, and it does by enumerating signal categories. The remaining gap is behavioral edge cases for an open-world fetch, which are not covered.

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% with a single required 'url' parameter already documented as 'Business homepage URL (https://...)'. The description adds no constraints such as whether subpages are crawled or whether the URL must be the root.

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 ('Fetch a business's website and extract signals') and enumerates exactly which signal categories are produced (mobile readiness, contact info, booking system, socials, chat widgets, pricing hints, FAQs). It also names the downstream consumer score_presence, which separates it from a raw fetch_page.

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?

'Output feeds score_presence' implies part of a workflow, so the agent can infer this is the step before scoring. But there is no explicit when-to-use or when-not versus fetch_page or extract_faqs, which overlap in subject matter.

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