create_social_media_post

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects (e.g., immediate posting vs scheduling), required authentication, or rate limits. The word 'create' is ambiguous given the action parameter.

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 extremely terse (5 words), under-informative for a tool with 7 parameters and nested objects. While concise, it does not earn its place since it adds almost no useful information.

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 (no output schema, no annotations, rich input schema), the description is completely inadequate. An AI agent cannot determine return values, prerequisites, or the tool's role in a workflow from this description alone.

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?

With 57% schema description coverage, the description adds no value beyond the schema. It does not clarify key parameters like action, message, or account_ids, nor explain the difference between accountless drafts and scheduled posts.

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 'Create a social media post' provides a verb and resource, but it is vague and does not distinguish this tool from siblings like update_social_media_post or create_social_media_tag. It lacks specificity about multi-platform support, actions, or scheduling.

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 offers no guidance on when to use this tool versus alternatives. It does not mention the three possible actions (schedule, add_to_queue, draft) or when each is appropriate, nor does it provide any exclusions or prerequisites.

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