Open Target

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

Discloses headless operation and session reuse, but with no annotations, the description does not cover side effects, error scenarios, resource impact, or whether the operation is read-only, leaving important behavioral gaps.

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?

Two sentences efficiently convey the core purpose and a key usage condition with no wasted words. Front-loaded and well-structured.

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 9 parameters and no annotations, the description is too sparse. It only addresses the target parameter's condition, leaving the purpose and implications of other parameters unexplained, and lacks overall usage guidance.

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%, so each parameter is already described. The description adds value by clarifying the target required condition for stateless vs session use, but does not enhance understanding of other parameters.

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 opens a public web document or official reference page headlessly, with specific verb and resource. It distinguishes from search and click tools but does not explicitly differentiate from the sibling tb_tab_open.

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 context on stateless versus session-based usage and when target is required, but lacks explicit guidance on when to choose this tool over alternatives or when not to use it.

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