selector_hint_list

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

With no annotations, the description carries the full burden, and it does disclose a meaningful operative fact: 'Does not need a browser to be running.' This is valuable given nearly every sibling tool requires an active browser session. It doesn't mention pagination or result-size behavior, but for a trivial read that gap is minor.

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?

Three short sentences, front-loaded with the core action and what is returned; the operational caveat is correctly placed last. No filler.

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?

There is no output schema, but the description compensates by naming the returned fields (key, domain, selector). Combined with the browser-not-required note, an agent has what it needs to call and interpret this tool; only exhaustiveness/pagination details are absent.

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% and the parameter's own description already defines the domain filter and the omit-to-list-all behavior. 'For every site, or only for one domain' restates the schema rather than adding new meaning, so baseline 3 applies.

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 gives a precise verb+resource ('List saved selector hints') and enumerates the returned fields (key, domain, selector), plus the scope options (every site or one domain). This clearly separates it from the sibling selector_hint_get (single key), selector_hint_save, and selector_hint_delete.

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?

It states a concrete trigger: 'Check this at the start of a run on a familiar site to reuse known selectors.' That is clear when-to-use guidance, but it never names the alternative (selector_hint_get for a known key) or any exclusions.

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