scrapeer_run_flow

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

Annotations do not provide safety hints (all false), so the description carries the burden. It adds valuable behavioral context: immediate return, asynchronous execution, cloud-based running, and name resolution behavior with multiple matches. These go beyond the structured annotations.

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?

Description is concise, front-loaded with the action, and uses clear sections (USE THIS/DO NOT USE). No wasted words; each sentence serves a purpose.

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?

For an async trigger tool, the description covers key aspects: return value (execution ID), execution location (cloud), and follow-up behavior (polling yourself). It doesn't explicitly mention how to poll, but sibling tools and usage guidance imply it. Complete enough given no output schema.

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 the baseline is 3. Description mentions accepting flow ID or name but does not add significant extra detail beyond the schema's parameter descriptions. No new semantics for parameters are introduced.

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?

Description clearly states the tool 'Trigger a cloud run of a scraping flow' with a specific verb and resource. It distinguishes from sibling scrapeer_run_flow_and_wait by noting it returns immediately with an execution ID and is for async/manual polling.

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 provides 'USE THIS TOOL WHEN' and 'DO NOT USE' conditions, naming the alternative scrapeer_run_flow_and_wait. This gives clear guidance on when to choose this tool over its sibling.

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