read_url_clean_markdown

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description goes further by disclosing the output budget (<400 tokens), the stripping of HTML clutter, SHA-256 provenance, and the key constraint that only public URLs are in scope — the last being a real operational boundary an agent must respect.

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?

One compact sentence with the core capability front-loaded. The bracketed '[ZERO API KEY REQUIRED]' prefix and words like 'cryptographic' and 'zero HTML clutter' lean promotional rather than informational, which costs it a point but does not bloat the definition.

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 single-parameter tool with rich annotations and full schema coverage, most of what an agent needs is present, including return format and size. However, an open-world fetch tool should say what happens on unreachable, paywalled, or JS-heavy pages and whether output is ever truncated — none of which is addressed.

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% for the single parameter, so the baseline is 3. The description adds no format, scheme, or length guidance beyond what the schema already states ('Public HTTPS URL or documentation page'), so it does not earn above baseline.

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?

A specific verb ('Converts') acts on a specific resource ('any public web URL or documentation page') and produces a named output ('clean, token-efficient Markdown'). It is unambiguous on its own, but it makes no attempt to distinguish itself from the sibling nullclear_safe_fetch, which plausibly also retrieves URLs.

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 states capability but never says when to choose it or when not to. With nullclear_safe_fetch among the siblings, an agent has no stated basis for picking one over the other, and there are no exclusions (private URLs, JS-rendered pages) surfaced.

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