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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful trait with no output schema present: results come back as markdown. It says nothing about latency, cost per page, failure modes for unreachable URLs, or how multiple pages are combined.

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 sentences, front-loaded with the capability and closed with the return format; no filler. The middle clause is a short use-case list, which is efficient but reads more like examples than guidance.

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, stating the markdown return format closes the biggest gap, and the read-only/open-world annotations cover safety. Remaining omissions (per-page cost, behavior when a fetched URL fails, how many findings to expect) are minor for a three-parameter research 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 goal, urls, and maxPages are already documented, including the key search-vs-fetch branch ('if omitted, will search the web'). The description adds no format, syntax, or interaction detail beyond that, so 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 set (search, read, fetch, verify) and a specific resource (the live web), then sums up the output ('structured findings as markdown'). An agent knows exactly what capability this tool provides without opening the schema, and no sibling tool (build/deploy/gtm/shadcn) overlaps.

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?

Concrete use cases are listed ('read documentation, fetch API references, verify library usage'), which implies when to call it, but there is no explicit when-not guidance and no named alternative for overlapping needs (e.g. local codebase lookups). Usage is inferred rather than stated.

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