zernio_create_post

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

No annotations are provided, so the description carries full burden. It states 'create' but does not disclose that the tool supports drafting (`isDraft`), immediate publishing (`publishNow`), or scheduling (`scheduledFor`). The schema contains these but the description omits them, leaving the agent unaware of key behavioral options.

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 concise (two sentences) and front-loaded with the purpose. It wastes no words but could benefit from more structured guidance on parameter dependencies.

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?

Given 9 parameters and no output schema, the description is too brief. It fails to explain key workflow aspects like the conditional requirement of `platforms` (required for non-drafts per schema), the role of `publishNow` vs `isDraft`, or what the tool returns. The description is incomplete for a tool with this complexity.

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 description coverage is 100%, providing detailed parameter info. The description adds value by explaining how to structure platforms and media objects and referencing zernio_upload_media_from_file, but does not cover other parameters like content, title, or scheduling fields.

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 a new social media post', which is a specific verb and resource. It distinguishes from other tools like zernio_reddit_submit_post by implying multi-platform support, but does not explicitly differentiate from other post-related tools (e.g., zernio_edit_published_post).

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 guidance on how to structure platforms and media inputs, including referencing a sibling tool for media upload. However, it does not specify when to use this tool over alternatives (e.g., zernio_validate_post, zernio_update_post) or mention prerequisites like connected accounts.

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