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

Annotations only declare destructiveHint=false, so the description carries the behavioral load and does so richly: account/token requirements, the tier-4 graduation condition, and explicit partial-failure semantics ('If a step is refused midway, the response says exactly what was created and what to do next; nothing is hidden'). This is precisely the beyond-annotations context that helps an agent decide whether to call it.

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 the core action and the archive/publish model, then progressively discloses tier, account, and failure behavior. Dense but each sentence carries a distinct fact; the parenthetical asides ('you have them — from GitHub, disk, another host') are slightly padding but harmless.

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?

With no output schema, the description compensates by describing response behavior (it reports what was created and how to apply), which is enough for an agent to act. It leaves the exact response shape and the tier-4 graduation outcome details implicit, keeping it short of fully complete for a tool with a multi-stage execution path.

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. The description goes beyond the schema by documenting the entry-resolution fallback ('index.html at the archive root, or the single/shallowest .html'), a rule not stated in the zipBase64 schema text and relevant to how the archive is interpreted. It does not add format or size guidance for name/expiresInSeconds, so it stops short of 5.

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?

States a specific verb and resource ('Bring an EXISTING app to Dropyour in one call: zip its files and pass the archive') and immediately distinguishes itself from the two nearest siblings, dropyour_publish (single-HTML) and dropyour_graduate (multi-file, tier 4). An agent can route to this tool versus those without opening any schema.

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?

Explains exactly when each path applies: single-HTML archive behaves like dropyour_publish with no account, while a multi-file archive requires an active app subscription and an account token, mirroring dropyour_graduate. It even states the fallback ('Without one, the entry HTML is live and the response says how to apply'), so the agent knows the outcome of both the authorized and unauthorized cases.

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