publish_with_media

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

No annotations are provided, so the description carries full responsibility. It only states the action without disclosing side effects, failure behavior, prerequisites, or what happens after publishing. It also does not mention whether scheduled_at allows scheduling instead of immediate publishing.

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 sentence, concise, and front-loaded with the main action. 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?

The tool has 5 parameters and no output schema, yet the description only gives a brief summary. It lacks guidance on parameter semantics, expected results, or error handling, making it insufficient for correct invocation.

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?

The description provides no parameter details beyond the concept of media URLs. With a schema description coverage of 0%, the description fails to explain account_ids, text, scheduled_at, or auto_adapt, leaving the agent without essential parameter meaning.

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 the combined action: uploading media from URLs and publishing in one step. This distinguishes it from sibling tools like upload_media_from_url and publish_post_now, which perform only one step. The verb phrase is specific and unambiguous.

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?

The description implies usage for combining media upload and publishing, but does not explicitly state when to use this tool versus alternatives like upload_media_from_url followed by publish_post_now. No exclusions or conditions are provided.

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