update-file-from-url

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

Describes key behaviors: preserves prior revisions, appears in upload log, replaces content only, fails if no file exists. Annotations already mark destructiveHint, but description adds valuable context.

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?

Description is dense, well-organized, and front-loaded with the core action. Every sentence adds value with 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?

Covers all necessary aspects: action, result (returns title and URL), constraints, alternative tools, error conditions. No output schema, but description sufficiently explains return values.

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 has 100% coverage with descriptions for all 3 parameters. Description does not add significant extra meaning beyond the schema, so 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?

Clearly states it fetches a file from a remote URL and uploads it as a new revision of an existing file. Distinguishes from siblings by mentioning alternative tools for different scenarios.

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 provides when to use alternatives: for editing wikitext use update-page, for disabled upload-by-URL use update-file, for initial upload use upload-file-from-url. Also notes prerequisite of wiki having upload-by-URL enabled.

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