create_post

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

With no annotations, description fully discloses behavior: draft vs scheduled, return of created post with id, prerequisites. It doesn't mention error handling or rate limits, but covers key behavioral aspects adequately. Slight deduction for lack of detail on validation 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?

Description is front-loaded with the main purpose, then logically progresses through draft/scheduled details, return value, prerequisites, and alternative tool. Each sentence adds value with no redundancy, achieving conciseness.

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 the tool's complexity (7 params, no output schema), the description covers core functionality, prerequisites, and alternatives. It mentions the return value minimally. Could include more on error scenarios or return structure, but overall adequate.

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% with detailed descriptions. Description adds value by explaining the draft/scheduled flow and the precedence of status over is_draft. It doesn't repeat schema details but provides contextual semantics beyond the parameter 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?

Description clearly states the tool creates a new post as draft or scheduled. It distinguishes from sibling publish_post by explicitly mentioning that to publish an existing draft immediately, use publish_post. This provides specificity and differentiation.

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?

Description provides explicit preconditions: media must already exist (import_media/list_media), platforms must be connected (list_social_accounts). It also notes the alternative publish_post for immediate publishing of drafts. This gives clear when-to-use and when-not-to-use guidance.

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