scrape_contacts_from_website

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

The description discloses batching behavior and a default email restriction, but without annotations it should provide more behavioral context (e.g., rate limits, auth requirements, read-only nature). The note is incomplete due to truncation, reducing transparency.

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?

The description is concise and front-loaded, but appears truncated at the end (note cut off), which detracts from clarity. Otherwise, efficient in word count.

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?

Given no output schema and three parameters (two poorly described), the description lacks critical information on return format, error handling, or rate limits. The truncated note suggests incomplete context for the optional parameters.

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?

Despite 100% schema coverage, the descriptions for 'match_email_domain' and 'external_matching' are unhelpful ('Example value: '), adding no meaning beyond parameter names. The main parameter 'query' is adequately described in the description but not linked to schema details.

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 it scrapes emails, phone numbers, and social profile links from a website root domain, distinguishing it from the sibling tool 'get_website_by_keyword' which likely finds websites by keyword rather than extracting contacts.

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 description mentions batching up to 20 domains and a note about email domain restriction, providing context for when to use the tool. However, it does not explicitly state when to use this tool over the sibling or when not to use it.

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