upload-file-from-url

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

Description contradicts annotation idempotentHint=true by stating the tool fails if the file title already exists, meaning repeated identical calls are not idempotent. This is a clear contradiction.

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?

Four well-structured sentences, each adding unique value. Front-loaded with core purpose, followed by constraints and alternatives. No redundancy.

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?

Covers core behavior, return values, prerequisites, failure conditions, and alternatives. Lacks details on size/rate limits but adequate for a standard file upload 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?

Input schema covers all 4 parameters with descriptions, achieving 100% coverage. The tool description does not add significant parameter-level detail, but the schema is sufficient.

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?

Clearly states the tool fetches a file from a URL and uploads to the wiki's File namespace, returning the title and URL. Distinguishes from siblings such as update-file-from-url and upload-file.

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 mentions prerequisite (upload-by-URL enabled), failure condition (title exists), and provides alternatives: use upload-file for local files, use update-file-from-url for replacing existing files.

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