dom

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

With no annotations, the description describes the three actions and their basic outcomes. It does not mention side effects, permissions, or performance implications (e.g., snapshot depth). The schema covers parameter details, leaving some 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?

The description is extremely concise (two sentences) and well-structured, with actions listed in parentheses and clearly separated. Every word adds value.

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 no output schema, the description gives reasonable expectations for each action's result ('basic info', 'detailed properties', 'full DOM snapshot'). Combined with the schema's param descriptions, it covers the essential usage context.

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?

The schema description coverage is 100%, so baseline is 3. The description adds brief context for each action but does not significantly enhance understanding beyond what the schema already provides for parameters like selector syntax.

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 'Inspect and query the DOM' with three specific actions (querySelector, getProperties, snapshot), each briefly explained. This distinguishes the tool from sibling tools like 'inspect' or 'console' by explicitly listing its capabilities.

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 gives no guidance on when to use this tool versus alternatives. It only describes what it does, without mentioning when not to use it or comparing to sibling tools like 'inspect' or 'content'.

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