upload-asset

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

With no annotations, the description fully discloses behavior: WebDAV channel, automatic folder creation, public serving of uploaded files, and the risk of LevelDB corruption for disallowed paths. Also mentions required password.

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?

Concise but packed with essential information. Front-loaded with channel and purpose. Every sentence adds value, though could be slightly more streamlined.

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?

Comprehensive for a tool with no annotations and no output schema. Covers purpose, usage, behavioral traits, and parameter details. Could mention failure handling, but return value is stated.

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%, but description adds value by clarifying remotePath is relative to Data/ root, providing an example, and warning against world data/ directories. Overwrite default is noted.

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?

Clear verb (Upload), resource (ASSET), and channel (WebDAV). Explicitly states it returns public HTTPS URL. Distinguishes itself from siblings like upload-asset-tree and download-asset by specifying it's for single asset uploads and not for world-DB files.

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?

Provides context (Plane B, file channel, write), conditions (ASSETS ONLY, not world-DB), privacy warning, and password requirement. Does not explicitly name alternative tools but implies alternatives for non-asset files.

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