scrape_thread

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

With no annotations, the description carries the full burden. It discloses that the tool opens a browser, navigates, intercepts GraphQL responses, and saves data locally—behavioral traits beyond the schema. It also notes the 'public' constraint. However, it does not detail potential side effects like rate limits, file overwrites, or cleanup.

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 compact and well-structured: purpose, mechanism, prerequisite, then a simple argument list. Every sentence serves a function, and it front-loads the key information.

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 the tool's complexity (browser automation, local save) and that an output schema exists, the description covers the prerequisite relationship and parameter details. It could be more complete by noting potential failure modes, but it is sufficient for an agent to invoke it correctly.

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 0%, so the description must explain parameters. It does: url is described as a 'Full URL' with an example, and max_scrolls as 'Maximum scroll iterations for loading more replies (default: 20).' This adds meaning beyond the bare 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 its function: 'Scrape replies from a public Threads post URL.' It also details the mechanism (opens a browser, intercepts GraphQL API responses) and differentiates itself from siblings by noting it must precede get_all_replies/search_replies.

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 explicitly states a prerequisite condition: 'This must be called before using get_all_replies or search_replies,' which tells the agent when to use it relative to other tools. It also implies it is the initial scrape step and works only on public posts.

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