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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the 100-page cap, robots.txt compliance, the exact return fields (URL, title, text), cost structure, and the behavioral difference store=true causes (7-day share link instead of inline data). This is exactly the kind of operational context annotations cannot carry.

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?

Front-loaded with purpose and scope, then options and cost. Dense and mostly waste-free, though the two pricing statements ('$0.005 + $0.001 per page' and 'Costs $0.025 USDC per call') read as partially redundant and slightly muddled rather than crisply separated.

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 steps in to name the returned fields, and it covers the limit, compliance behavior, and the store toggle plus pricing. An agent has everything needed to call it correctly and anticipate the response shape.

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 the baseline is 3, but the description adds real meaning: store=true changes the return channel rather than just 'return a link', and it frames path_prefix and the page cap in behavioral terms. The added value over the schema is genuine though modest.

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 (crawl) and resource (a website) with the output form (clean Markdown) and scope rules (same-site links, up to 100 pages, robots.txt). Very clear what the tool does, but it never names a sibling like scrape or sitemap to draw the boundary between single-page and site-wide extraction.

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?

The scope rules ('follows same-site links from a start page', 'up to 100 pages') imply when this multi-page tool fits versus one-shot extraction, and the store=true line explains an option's purpose. However, there is no explicit when-to-use/when-not statement or named alternative, so the agent must infer the routing decision.

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