create_media_drop

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and non-idempotent, so the description need not re-state that this is a write. It adds real context instead: no dashboard login required for the uploader, a 20-file link cap, an explicit accepted-format whitelist with the HEIC exclusion, and a 50MB size ceiling. It stops short of saying whether drops expire or can be reused, which would complete the picture.

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?

The purpose and the return value are front-loaded in the first sentence, and the workflow instruction follows immediately. The middle sentences are dense but each carries a real constraint; only the trailing sibling exclusions feel slightly tacked-on rather than integrated into the flow.

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 carries the burden of explaining the return value and does so concretely (drop_url with its URL shape), plus the follow-up call needed after the user uploads. For a mutation tool with three optional parameters, that covers everything an agent needs to call it and act on the result.

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 description coverage is 100%, so all three parameters are already documented, and the description adds no new meaning about filename, max_files, or workspace_id. The format and size limits it does supply are tool-level constraints rather than parameter semantics, so the baseline 3 applies.

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?

The description names a specific verb and resource ('Create a human drop page') and defines its scope precisely: an upload link for external users, up to 20 files, no dashboard login. It explicitly separates itself from two siblings by name ('not the chat paperclip and not create_signed_upload'), so an agent can pick it out 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?

It gives the full operating sequence -- create the drop, send drop_url to the user, wait, then call list_media -- which is the when-to-use guidance an agent actually needs. It also states the negative case by naming the two alternatives it is not, so routing decisions are fully determined.

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