create_post

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

With no annotations, the description carries the full burden. It discloses key behaviors: media is fetched from remote URLs or read from disk, exactly one media source per call, and omitting scheduledFor publishes immediately. This goes beyond schema information, though it does not cover error handling, authentication, or side effects like partial failures.

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 compact (two sentences) and front-loaded with the tool's primary action. It avoids redundancy with the schema and earns every word by explaining media constraints and scheduling behavior.

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 description covers the main creation flow and scheduling, but with no output schema, it omits what the caller should expect in return (e.g., post IDs, confirmation of scheduling). It also doesn't mention timezone or carousel options, though those are in the schema. The lack of return/error information leaves a gap for a tool with 10 parameters.

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%, so baseline is 3. The description adds meaningful clarification: mediaUrl is server-fetched while mediaPath is read from disk, exactly one media source is required, and scheduledFor omitted means immediate publish. This enriches the parameter meaning beyond the schema 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 clearly states a specific verb ('Create and publish') and resource ('post') along with target platforms (YouTube, TikTok, Instagram). It distinguishes this tool from siblings like update_post and delete_post by focusing on creation and immediate/scheduled publishing.

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 provides clear context for when to use this tool (creating new posts) and even explains scheduling vs. immediate publishing. It does not explicitly name alternatives or exclusions, but the intended use is unambiguous given the tool name and sibling list.

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