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

Since no annotations are provided, the description must fully disclose behavior. It states only that the output is 'clean Markdown', but does not mention what happens if the URL is invalid, blocked, or requires authentication. It also does not clarify whether the tool handles JavaScript-rendered pages, rate limits, or returns any error messages. This lack of transparency could lead to unexpected failures.

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 extremely concise at only six words, which is efficient but borderline under-specified. It front-loads the purpose, but could be improved by adding a few more words about what the tool does without becoming verbose.

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 the lack of output schema, contextual complexity, and many siblings, the description is incomplete. It does not explain what 'clean Markdown' means (e.g., stripping ads, navigation, only main content), nor does it address potential issues like JavaScript rendering or large page handling. For a tool that fetches arbitrary web content, more detail is needed for reliable agent usage.

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 0%, and there is only one parameter ('url') with no description in the schema. The tool description does not add any semantics about the URL format (e.g., must be fully qualified, supported protocols, etc.). With a single required parameter, the baseline expectation is moderate, but the description should at least clarify that it accepts any valid HTTP/HTTPS URL.

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 'Any public URL as clean Markdown' clearly indicates that this tool takes a URL and returns its content in Markdown format. It is distinct from siblings like 'screenshot' (which captures an image) and 'url_safety' (which checks URL safety). The verb 'read' is specific, but the resource is implied as web content.

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?

No guidance is provided on when to use this tool versus alternatives like 'screenshot' for visual content or 'search' for finding information. There is no mention of prerequisites, limitations (e.g., paywalled sites, dynamic content), or expected use cases. The description is too minimal for an agent to decide between read and other tools.

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