novada_browser_flow

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

The description adds behavioral context beyond annotations: session expiration (10 min), action limit (20 per call), and that sessions preserve state. While annotations indicate non-destructive and non-idempotent behavior, the description clarifies operational constraints. No contradiction with 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?

The description is well-structured with clear sections (Best for, Actions, Sessions, Fallback, Not for). It is concise with no wasted words, yet covers all essential information for an AI agent.

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?

Despite no output schema, the description adequately covers use cases, constraints (action limit, session expiry), and fallback. It could mention the return format, but given the complexity and the presence of sibling tools for comparison, it is nearly complete.

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 baseline is 3. The description adds value by summarizing action types and explaining session_id usage, which goes beyond the schema's property descriptions. This helps agents understand the tool's capabilities beyond raw parameter definitions.

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 the verb 'Execute' and the resource 'multi-step browser automation with Novada's cloud browser'. It specifies use cases like JS-heavy sites, login flows, and multi-page sequences, distinguishing it from siblings such as novada_browser, novada_extract, and novada_scrape.

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?

Explicit 'Best for', 'Not for', and 'Fallback' sections provide direct guidance on when to use this tool and when to use alternatives. It also details session reuse and expiration, giving agents clear decision criteria.

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