read_url

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

Despite no annotations, the description fully discloses behavior: unlocking ladder, Markdown output, stripping control characters, prompt-injection fencing with warning, and error string on failure. No missing critical traits.

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?

Information-dense but well-structured: front-loaded with primary purpose, then escalation ladder, usage context, output details, and error case. Could slightly trim but overall efficient.

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 and only one parameter, the description covers all necessary context: operation, success/failure behavior, output format, security handling. No gaps identified.

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?

Only one parameter 'url' with schema coverage 100%. Schema description already specifies 'Absolute http(s) URL'. The tool description does not add new meaning beyond the schema, so baseline 3 applies.

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 reads one web page and returns clean Markdown, with a specific escalation ladder. It distinguishes from siblings like 'fetch_asset' by targeting blocked or client-side rendered pages.

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?

Explicitly states when to use (HTTP fetch blocked by 403/429, bot-walls, client-side rendering). Provides context that it beats most common bot-walls, but does not explicitly mention when not to use or name an alternative tool.

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