create_post

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

No annotations are provided, so the description carries the full burden. It only states 'create and schedule', but does not disclose effects like immediate vs. timed publishing, reversibility, authentication requirements, or error handling. This is insufficient 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 a single sentence, concise and front-loaded with the core action. However, it sacrifices completeness for brevity, which is acceptable given the structure. No wasted words.

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?

With no output schema, no annotations, and a minimal description, the tool lacks important context. There is no information about scheduling behavior, success/failure confirmations, or how the post content is handled. Essential details are missing for a creation 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 coverage is 100%, so baseline is 3. The description adds no parameter meaning beyond what the schema already provides. The schema descriptions are adequate, including a critical usage note for platforms, but the tool description itself does not enhance semantics.

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 'Create and schedule a post to one or more social media platforms', specifying the verb (create and schedule), resource (post), and scope (multiple platforms). It distinguishes from sibling tools like get_post, delete_post, and list_posts which handle different operations.

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 creating scheduled posts but does not explicitly state when to use this tool versus alternatives. There is no guidance on prerequisites or exclusions. The parameter description does include an important note about calling list_connections first, but that is not part of the main description.

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