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

Goes well beyond the annotations: it warns that re-uploading overwrites the file, that it publishes nothing, and lays out path rules (charset, no umlauts/spaces, hidden-file exception for .well-known/, no _tp/), allowed file types, encoding mapping, and a 1 MB per-call limit. This is the behavioral context an agent needs for a mutating staging write.

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?

Front-loaded with purpose and sibling routing, then constraints. It is long, but essentially every clause carries a hard rule (charset, extensions, size, encoding) with no filler; a slightly tighter phrasing of the path examples could trim it.

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?

For a 5-param staging upload tool with no output schema, the description covers purpose, alternatives, mutation semantics, validation constraints, and the fact that it does not publish. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds real meaning: concrete path syntax and examples, allowed character set, and the utf8/base64 encoding-to-content mapping with a size cap. It enriches the enum and content parameters rather than just restating them.

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?

Opens with a specific verb+resource+scope: loads a file into an open deploy (created by deploy_begin). It explicitly distinguishes itself from siblings by naming deploy_import_asset for web images and deploy_publish for publication.

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?

States one call per file, routes web images to deploy_import_asset ('nicht hotlinken'), forbids large binaries as Base64, and clarifies that publishing is deploy_publish's job after user confirmation. When-to-use and when-to-use-alternatives are both explicit.

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