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

Annotations only declare it is a non-read, non-destructive, closed-world write. The description adds the traits that actually matter here: the token lifetime (24h), that new tickets renew the account token family WITHOUT revoking in-flight uploads, and that tickets support batched reuse. That is non-obvious mutation semantics that no annotation conveys.

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?

Three dense sentences with the core action front-loaded, followed by lifecycle/constraint details and the sibling route. No filler, no restatement of the title, and each sentence adds a distinct fact (what is minted, token-family behavior, revocation path).

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 single-optional-param write tool with no output schema, the description supplies everything an agent needs: what is returned in effect (endpoint + bearer token), how long it lives, how it interacts with existing uploads, and how to undo it. Nothing material 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?

Only one optional parameter (folder_id) and schema description coverage is 100%, so the schema already documents the UUID and the Folder-Id header requirement. The description adds no parameter-level detail beyond that, 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?

States a specific verb+resource ('Start a media upload... mints an upload ticket') and immediately qualifies the output (TUS endpoint + 24h bearer token) and protocol (TUS 1.0.0 client). It also names the sibling it complements (revoke_upload_tickets) and maps to the underlying REST route, so an agent can distinguish it from create_folder/create_stream without opening a 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 operational guidance: reuse one ticket for a batch when practical, and use revoke_upload_tickets to invalidate the token family immediately. It names the alternative tool and the condition that selects it, but never states when NOT to mint a ticket (e.g., if a valid unexpired ticket already exists) or any preconditions beyond folder ownership implied by the schema.

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