upload_media

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

No annotations provided, so description must convey all behavioral traits. Describes the upload process and auto-detection of MIME type, but omits details like file size limits, supported formats, async behavior, or whether the operation is destructive. Adequate but not comprehensive.

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?

Two sentences: first explains the process, second gives usage guidance. Every word earns its place. No redundancy or fluff. Perfectly concise.

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?

No output schema, but description specifies return value { media_url }. Explains parameter interaction (mutual exclusivity implied). Missing details on file size limits, supported formats, or scalability. Fairly complete for a straightforward upload tool.

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 covers all three parameters with basic descriptions. Description adds value by explaining that file_path and source_url are alternatives (OR), and that content_type overrides auto-detection. Also relates output to other tools. Provides meaningful context beyond 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?

Description explicitly states 'One-step media upload' which is specific verb plus resource. It details the process: generates signed URL, uploads bytes, returns media_url ready for other tools. Distinguishes from sibling 'create_media_upload_url' by being a complete upload step.

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?

Clearly states 'Use this whenever you need to attach an image or video.' Mentions the output is ready for create_post/publish_now/schedule_post. Lacks explicit when-not-to-use or alternative comparisons, but the usage context is well-defined.

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