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

Annotations only declare idempotentHint and destructiveHint=false, but the description adds substantial behavior: the URL/origin contract keeps browser data intact across updates, drop type is preserved, contract checks under dropyour_link can refuse a breaking version and restore the previous one, plus the consumer_contract_broken error and token requirements. This is rich context well beyond the structured fields.

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?

A single dense paragraph, front-loaded with the core action and immediately followed by the origin-contract and type-preservation constraints. Every sentence carries information, though the contract-check clause is packed and could be split for scanability.

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 mutation tool with no output schema and annotations covering idempotency/safety, the description covers what changes, what is preserved, failure behavior, and error signaling. It stops short of documenting permissions beyond token ownership and says little about the returned result, but it is otherwise call-ready.

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 75% (dropId relies on the pattern alone). The description adds meaningful semantics on top of the schema: html applies only to single-file drops, zipBase64 requires tier-4 graduation, and managementToken is unnecessary for account-owned drops. This exceeds the baseline-3 expectation for high coverage.

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 (replace) and resource (an existing drop's content), and distinguishes itself from siblings like dropyour_patch, dropyour_publish, and dropyour_rollback by describing the in-place, URL-preserving semantics. An agent can tell what this does without opening the 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?

Gives clear conditional context: HTML for single-file drops, base64 .zip only once the app has GRADUATED to tier 4, and account-token ownership removing the need for managementToken. It does not, however, explicitly route the agent away from alternative tools (patch/publish/rollback), so it lacks true when-not guidance.

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