query

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

No annotations, but description covers return format, stable handles, and selector engine capabilities. Lacks explicit statement of non-mutation, but behavior is well inferred.

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?

Single paragraph with no redundant sentences; information is front-loaded (action and return format) followed by details on refs and selector capabilities.

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 query tool with one parameter and no output schema, the description fully explains inputs, outputs, and integration points (refs for click/type/submit), meeting all needs.

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 covers the single parameter with a brief description; the tool's description adds significant detail on supported selector syntax, going beyond the schema's minimal 'CSS selector'.

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?

Description clearly states the action ('Run a CSS selector'), the target ('current page's parsed DOM'), and the return format with element refs for interaction, distinguishing it from siblings like query_text.

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?

Implied usage for DOM querying and interaction via refs, but no explicit guidance on when to prefer this tool over siblings like find_text or query_text.

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