Url Markdown

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by disclosing that the tool does not execute JavaScript, does not bypass access controls, rejects SSRF-sensitive destinations, and uses caching. It does not contradict any annotation.

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 three well-structured sentences, front-loaded with the core action. Every sentence provides necessary information without redundancy, making it highly 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?

For a tool with good annotations, complete parameter schema, and an output schema (not shown but present), the description covers all necessary behavioral context: public URLs only, no script execution, caching advice, and SSRF protection. No gaps remain.

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 for parameters is 100% with descriptions for both 'url' and 'fresh'. The description largely repeats the schema's content (e.g., 'absolute public HTTP(S) URL', 'set fresh=true only when a new upstream fetch is required'). It adds minor context about cache reuse but does not significantly extend the schema's meaning.

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 the verb 'Convert', the resource 'readable HTML content', and the output 'bounded Markdown'. It distinguishes from sibling URL tools by noting it only works on public HTTP(S) and does not execute JavaScript, aligning with its specific 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?

The description provides explicit usage constraints: only public HTTP(S) URLs, no JavaScript execution, no access control bypass. It also gives advice on the 'fresh' parameter. However, it does not explicitly state when not to use this tool or mention alternatives among the many sibling tools, so it's slightly less than perfect.

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