scrapeer_get_flow

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

Annotations already define read-only/idempotent/non-destructive behavior. The description adds a valuable behavioral nuance: 'Only blocks reachable from the Start block are returned. Orphaned/disconnected blocks on the canvas are pruned.' This goes beyond annotations and helps set expectations for debugging.

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 front-loaded with the purpose, then proceeds logically to parameter handling, behavioral note, and usage guidance. It uses clear formatting with 'NOTE:', 'USE THIS TOOL WHEN:', and 'DO NOT USE:'—every sentence earns its place without redundancy.

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 simple interface (1 param, no output schema) and available annotations, the description covers all essential aspects: what it returns, key pruning behavior, accepted input formats, and when to use. No critical information is missing 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 100% for the single 'flow' parameter. The description mentions accepting ID or name, which echoes the schema but adds no additional details. Baseline 3 is appropriate since the schema fully documents the parameter.

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 'Get details about a specific scraping flow' and enumerates what is returned (blocks with full config, selectors, variables, edges, metadata). It explicitly distinguishes from the sibling 'list all flows' with 'DO NOT USE: to list all flows (use scrapeer_list_flows)'.

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?

Provides explicit 'USE THIS TOOL WHEN' conditions (know flow by name/ID, inspect selectors/block config, debugging) and an explicit 'DO NOT USE' with an alternative tool. This gives the agent clear decision guidance.

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