scrapeer_create_flow

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

Annotations only provide readOnly=false, idempotent=false, destructive=false. The description adds that the flow is created empty, requires follow-up updates/patches, and returns the flow's ID. This goes beyond annotations and offers useful behavioral context, though it doesn't mention edge cases like duplicate title handling.

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 four sentences, starting with the core action, then the return value, followed by follow-up guidance, and ending with explicit usage conditions. It is concise and well-structured, though the 'USE THIS TOOL WHEN' section partially repeats the purpose, which is a minor 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?

For a simple create tool with a single parameter and no output schema, the description is complete: it states the action, the return value, the empty state, and the relationship to sibling tools. The guidance covers the primary use cases and failure mode (overwriting).

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?

The schema already fully describes the sole 'title' parameter as 'Display name for the new flow.' The description merely says 'with the given title' and adds no extra semantic detail, so the baseline of 3 is appropriate given 100% schema coverage.

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 explicitly states 'Create a new (empty) flow with the given title' and notes it returns the new flow's ID. It clearly distinguishes from sibling update/patch tools by specifying the flow is empty and that updates are for later, making the purpose unambiguous.

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 provides explicit 'USE THIS TOOL WHEN' and 'DO NOT USE' sections, naming scrapeer_update_flow as the alternative for overwriting existing flows. This gives clear, actionable guidance on when to use this tool versus siblings.

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