Fetch full webpage content and convert it to markdown format, with an option to limit characters returned.
Lấy nội dung đầy đủ của một trang web dưới dạng markdown.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Địa chỉ trang cần đọc. | |
| max_chars | No | Số ký tự tối đa trả về (cắt bớt nếu vượt quá). |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the output format (markdown) and the max_chars truncation behavior is in the schema. It doesn't mention potential issues like paywalls, dynamic content, or rate limits, but for a simple fetch tool the description is reasonably transparent.
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 short, clear sentence in Vietnamese. It is front-loaded with the main action and output format. No wasted words.
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?
The tool is simple with 2 parameters, 100% schema coverage, and an output schema. The description covers the core purpose and output format. It could mention edge cases like non-HTML content or errors, but for a straightforward fetch tool this is largely complete.
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 100%, so the schema already documents both parameters. The description adds the output format (markdown) but doesn't add much beyond the schema. Baseline 3 is appropriate.
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 states a specific verb ('Lấy' = fetch/retrieve) and resource ('nội dung đầy đủ của một trang web' = full content of a webpage) and the output format (markdown). It is clear what the tool does, though it doesn't explicitly distinguish itself from siblings like web_search or search_stats.
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 implies usage: use this tool when you need the full content of a webpage as markdown. It doesn't explicitly state when not to use it or mention alternatives like web_search for searching or search_stats for statistics. The context is clear but exclusions/alternatives are not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.