upload_media

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

No annotations provided, so description carries full burden. It discloses that file_path only works on local server and implies a write operation. However, it lacks details on idempotency, duplicate handling, or media size limits, which are useful for a mutation tool.

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 description is two sentences and to the point. The second sentence is slightly dense but effectively packs key usage notes. No redundant information.

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 exists, yet the description only vaguely mentions 'get a media ID'. It doesn't specify the return format or error cases. For a tool with 5 optional parameters, more detail on expected outcome would improve completeness.

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 100%, but description adds context: clarifies url vs data usage, warns about direct file links, and notes that filename is required for bare base64. This adds meaningful value beyond the schema's own descriptions.

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 explicitly states it uploads an image/video to Social0 and returns a media ID for posts. It clearly distinguishes from sibling tools like create_post or delete_post by focusing specifically on media upload.

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?

Provides clear guidance on parameter choice: url/data for remote hosts, file_path only for local files. Warns about remote sandboxes. However, it doesn't explicitly state when to use this tool versus alternatives like posting directly.

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