chrome_inspect

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the kind of output expected by enumerating nearby text, actions, form context, ancestors, and suggested click target. It does not explicitly state that the operation is read-only or describe side effects like focusing or activating the tab, though 'Inspect' implies a non-mutating operation.

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 informative sentence with no filler. The list of deep-context outputs adds value and is front-loaded; it does not repeat schema details or annotations.

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?

For a tool with no output schema and no annotations, the description provides the essential output categories and the schema fully documents parameters. Still, some invocation context is missing, such as read-only guarantees, tab-selection priority, or how the suggested click target is derived, leaving moderate gaps.

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 all seven parameters are already documented. The tool description adds little parameter-level meaning; it only reinforces that a uid or selector is the inspection target, which the schema already conveys.

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 states a clear verb ('Inspect'), a specific resource ('one snapshot uid or selector'), and lists the deep context it returns: nearby text, nearby actions, form context, ancestors, and suggested click target. It does not explicitly name or differentiate from sibling tools, though the 'deeply' clause separates it from tools like chrome_snapshot and chrome_find.

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 implies when to use it: when you have a specific uid or selector and need deep contextual information about that element. However, it does not explicitly state when not to use it or mention alternative tools such as chrome_snapshot/chrome_find for lightly inspecting elements.

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