Fetch Document

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

The description states 'Downloads remote URLs into MEDIA_GEN_DIRS', indicating a write operation, but annotations set readOnlyHint=true. This contradiction severely undermines transparency and could mislead an agent.

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?

Two concise sentences: the first states the core purpose, the second adds key details. No fluff, front-loaded, and every word earns its place.

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 description covers the main behavior, output types, and download destination. However, missing details like supported document formats, error handling, and a description of MEDIA_GEN_DIRS, along with the contradiction, prevent full completeness. Still adequate for a simple tool.

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%, so the schema already describes all parameters. The description adds context about output formats (resource_link vs embedded resource) but does not explain the 'file' parameter further. It meets the baseline but adds limited value.

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 fetches documents from URLs or local file paths, differentiating it from sibling tools like fetch-images and fetch-videos. However, it does not explicitly name these alternatives, slightly reducing clarity.

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 explicit when-to-use or when-not-to-use guidance is provided. The purpose is implied by the tool name and sibling context, but an agent might not know if this tool supports all document types or if there are prerequisites.

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