browser_set_date_range

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

With no annotations, description must carry full burden. Only states 'best-effort' but does not elaborate on failure modes, side effects (modifying page state), or required page state (must already have date inputs present).

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?

Single sentence of 11 words, front-loaded with key qualifier 'best-effort'. No redundant 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?

No output schema and no description of return values or results. Does not explain how the tool interacts with the page (e.g., clicks, inputs). Incomplete for a tool that modifies UI state.

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 67% (start and end dates have format descriptions; submit has none). Description adds context about interactivity but does not explain the submit parameter's role in the date-setting process.

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 action ('set'), resource ('date range'), and context ('interactive pages with date inputs'). It distinguishes from sibling tool 'browser_extract_tables_for_date_range' which extracts after setting.

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?

No explicit guidance on when to use this tool versus alternatives. 'Best-effort' implies unreliability but no further context. Does not mention prerequisites or cases to avoid.

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