browser_get_images

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

With no annotations, the description carries the full burden but only states that it lists images without mentioning side effects, limitations (e.g., only static DOM images), or whether it awaits page load. It is minimal and lacks behavioral context.

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 one sentence plus a terse args list, with no extraneous information. It is front-loaded and every word earns its place.

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 presence of an output schema (which likely details the returned list of images), the description adequately covers the tool's purpose and basic usage. For a simple tool with one optional parameter, it is sufficiently complete, though session requirements could be clearer.

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?

Although schema description coverage is 0% (no parameter descriptions in schema), the description adds only 'Browser session ID' for session_id, which is already implied by the schema title. It does not explain its optional nature or default behavior, adding marginal value.

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 'list' and the resource 'images on the current page', with specific details about URLs and alt text. It distinguishes itself from sibling tools like browser_snapshot (screenshot) and browser_vision (AI analysis) as a simple data extraction tool.

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 implicitly suggests using this tool when image URLs and alt text are needed from the current page, providing no explicit guidance on when to use alternatives like browser_vision. The context is clear enough for a simple list tool but lacks comparative or exclusionary statements.

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