grab_site

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

Describes the process (unlock ladder, download, extract), output (JSON manifest or error), side effects (saves files). No annotations, so burden is on description; it does well but lacks details on auth, rate limits, or performance.

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?

Concise at 4 sentences, front-loaded with main action, then guidance, defaults, and error handling. Every sentence earns its place.

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?

No output schema, but description explains return format (JSON manifest with local file paths or error string). Mentions unlock ladder but doesn't elaborate; could clarify manifest structure. Overall adequate.

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 descriptions. Description adds context like 'read=true saves page.md' and explains default out_dir behavior, adding value beyond schema.

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 clearly states the tool grabs a page for design inspiration, fetching assets, extracting palette and fonts, returning a manifest. It distinguishes from sibling fetch_asset for single files.

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?

Explicitly says use for a whole page's design/assets, and for a single known file use fetch_asset. Provides clear context and alternative.

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