create_post

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

With no annotations provided, the description carries the disclosure burden. It transparently reveals that the tool saves a draft (not directly schedules), mentions that each created post includes an editInVisualEditor URL, and points to the approve_post step for scheduling. It does not cover permissions or side effects, but the creation behavior is sufficiently clear.

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 four sentences, front-loaded with the primary purpose, and each sentence adds distinct value (function, platforms, next steps, special return field). There is no redundancy or filler.

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 no output schema, the description supplies key return information (editInVisualEditor URL) and workflow context (approve_post, check_social_accounts). One minor gap is that the schema includes a scheduledAt parameter for immediate scheduling, which the description does not mention, potentially causing slight ambiguity. Overall, it is fairly complete for the tool's 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 coverage is 100% and every parameter (brandId, content, platforms, scheduledAt) already has a description. The description reiterates the supported platforms but adds no new parameter-level meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 the tool's function: 'Save a post draft with custom content to one or more platforms.' It also lists the exact supported platforms and distinguishes itself from related tools like approve_post and check_social_accounts by explaining the post-creation workflow.

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 explicit workflow guidance: 'After creating, call approve_post with a future ISO 8601 datetime to schedule it' and advises checking connected platforms first via check_social_accounts. This clearly defines when to use this tool versus alternatives.

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