Create media upload

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

Discloses that the tool is a staging helper, returns an upload URL, and that staging media is deleted after 24 hours unless copied into durable storage via upload_video. No contradiction with annotations.

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?

Single paragraph, information-dense but could benefit from bullet points or clearer separation of usage guidance. Front-loads core purpose effectively.

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?

Covers purpose, usage restrictions, alternatives, lifecycle (24-hour deletion, durable storage via upload_video), and return value (upload_url). Complete for a helper tool with output schema present.

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 has 100% coverage of parameters with descriptions. The description adds context about the upload URL and client responsibilities but does not significantly enhance parameter meanings beyond the schema.

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 clearly states it is an 'Internal/app staging helper' that returns an upload URL for direct PUT, differentiating it from siblings like open_upload_studio and upload_video.

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?

Explicitly warns against using from ChatGPT/claude.ai model, provides alternative (open_upload_studio for attachments), and specifies appropriate use cases (MCP clients holding file bytes). Also notes 24-hour expiry and durable storage via upload_video.

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