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

Beyond the annotations (readOnlyHint=false, openWorldHint=true) it discloses a rich behavioral profile: 4-credit cost charged only on a successful return, free for already-looked-up pages, free/no-op for skip-only calls, and persistent exclusion of written-to/skipped pages. This far exceeds what the annotations convey and matches readOnlyHint=false without contradicting it.

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?

Information-dense but poorly structured: the leading clause is a long appositive stack with no upfront verb, and the cost sentence breaks mid-thought ("charged only when it returns. for a batch with new pages to look up..."). It earns its length with useful facts but is not front-loaded or cleanly segmented.

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-value burden well, enumerating the fields returned (questions, author byline, verified email), the fallback when no email exists, exclusion rules, and billing semantics. Minor gaps remain about exact output shape, but it is substantially complete for a 2-param read 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 coverage is 100%, so both parameters are already documented. The description adds color on skip semantics ("never offered again") and confirms count behavior, but adds little syntax or format detail beyond the schema, so the baseline of 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 concretely states what it returns: "best X"/"alternatives" pages that AI engines cite, ordered most-cited-first, with buyer questions, page author, and verified work email. The verb is implicit rather than front-loaded (it's a target/list-finder), but the resource and output content are unambiguous and clearly distinct from sibling finders like reach_find or launch_targets.

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 situational rules (pages already written to via record_action or skipped never return; use the site's contact page if no verified email exists) but never states the core when-to-use trigger or contrasts it explicitly with sibling discovery tools. Usage is implied rather than framed as a decision.

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