exploration_quick

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

Annotations declare readOnlyHint and openWorldHint, which the description supports by mentioning a sandbox without backend permissions. It adds behavioral context like automatic upgrade prompting and the 6-stage process. No contradiction. It provides value beyond annotations, though could mention error handling or time estimates.

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 a single, well-structured paragraph. It front-loads the main purpose, lists stages succinctly, and ends with the upgrade note. Every sentence adds value 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 tool has 4 parameters (all documented), no output schema, and safety annotations, the description covers the overall behavior well. It explains the 6 stages and the sandboxed execution. Missing details about output format are compensated by the lack of output schema. Adequate for a quick exploration tool.

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?

All 4 parameters have descriptions in the input schema, achieving 100% coverage. The main description does not add significant meaning beyond the schema, such as clarifying the difference between 'url' and 'target' (both are target URLs). Baseline 3 is appropriate.

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 tool's purpose: performing a 6-stage front-end shallow exploration on a target URL, listing specific stages. The name 'exploration_quick' and the description distinguish it from more specific sibling tools like browser_navigate or browser_visual.

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?

The description mentions it operates in a pure browser sandbox without backend permissions and that it prompts for upgrades when high-value clues are found. It implies usage for surface-level exploration, but does not explicitly state when not to use it or compare with alternatives. This is adequate but could be more explicit.

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