update-file

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

Adds context beyond annotations: preserves prior revisions, appears in upload log, replaces bytes only, operator directory restriction, fails if file doesn't exist. No contradiction with readOnlyHint=false, destructiveHint=true.

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?

Well-structured with core action first, then conditions and alternatives. Slightly verbose but every sentence adds value.

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 prerequisites, error conditions, returns, related tools. No output schema but mentions return of file title and URL.

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% description coverage. Description adds meaningful context: filepath must be absolute inside configured directory, title can have/without 'File:' prefix, comment is reason for revision.

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?

Description explicitly states 'Uploads a new revision of an existing file' and distinguishes from sibling tools: upload-file for initial upload, update-file-from-url for remote source, and update-page for wikitext editing.

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?

Clear guidance: fails if no file exists, so use upload-file for initial upload; to upload from remote URL use update-file-from-url; for editing description page use update-page.

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