dompruner_fetch

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

With no annotations, the description carries the full burden and does so excellently. It discloses key behaviors: DOM pruning with 90%+ token reduction, preservation of original text (no summarization), BM25 section filtering, and the unusual URL-sampling behavior when url is omitted. This goes beyond basic expectations and covers potential surprises.

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 well-structured, starting with a strong directive, then behavior, workflow, and filtering capability. It is slightly lengthy but every sentence contributes value; no filler or tautology.

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 2-parameter tool with no output schema and no annotations, the description is impressively complete. It covers alternatives, usage scenarios, special behaviors, and expected output format (Markdown). The workflow guidance leaves little room for agent confusion.

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%, so the baseline is 3. The description adds meaningful context beyond schema: it explains how query enables BM25 filtering and can trigger URL sampling from the host LLM when url is absent. This enriches the parameter definitions without redundancy.

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 it fetches a URL and returns DOM-pruned Markdown, with a specific verb, resource, and outcome. It explicitly differentiates itself from WebFetch and aligns with sibling tools by name (fetch vs. sitemap/analyze), leaving no ambiguity about its function.

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 gives an explicit directive to use this instead of WebFetch, and provides a step-by-step workflow for both known and unknown URLs. It also explains when to use the query parameter for BM25 filtering, offering clear context for appropriate usage.

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