create_post

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

No annotations provided, so description carries full burden. Discloses draft/scheduled creation and parameter interplay (status overrides is_draft). However, missing details on authentication, rate limits, idempotency, and side effects beyond creation.

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?

Two sentences, front-loaded with purpose. No redundant words. Efficiently communicates key usage variations.

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?

Explains main functionality and parameter usage but lacks output description (no output schema). Missing error conditions or validation details for a 7-parameter tool with multiple modes.

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?

Adds meaning beyond schema by explaining is_draft as convenience for draft status, relationship with scheduledFor, and max 10 carousel constraint. The schema already covers 71% of parameters, but description clarifies usage logic.

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 draft or scheduled post', specifying the verb and resource. It distinguishes between draft and scheduled modes using parameters. Differentiates from siblings like update_post or publish_post by focusing on creation in draft/scheduled states.

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 when to use is_draft vs scheduledFor, and libraryItemId vs mediaIds (max 10). However, does not explicitly mention when not to use this tool (e.g., publishing or editing), though siblings like publish_post and update_post exist.

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