Extract DOM Content

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

With no annotations, description must cover behavior. It states extraction scope but does not explicitly mention that it is non-destructive or any potential limits. However, for a read operation, the description is adequate.

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?

Efficient use of space: purpose stated first, then usage guidance, then parameter summary, then example. No wasted words.

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?

Simple tool with no output schema; description mentions extracted content types (HTML, text, DOM structure). Could be more explicit about return format but sufficient for common use cases.

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 baseline is 3. The description adds a brief note on selector usage and example, but does not significantly enhance schema-provided parameter info.

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?

Clearly states 'Extract HTML, text, and DOM structure from a webpage', uses specific verb and resource. Distinguishes from sibling tool captureScreenshot by stating when to use each (text vs visual).

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?

Explicit 'USE WHEN' and 'USE captureScreenshot WHEN' sections provide clear context and alternatives. Includes an example invocation.

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