social_media_posting_create_post

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

Annotations declare readOnlyHint=false and destructiveHint=false, indicating it's a write operation. The description adds nothing beyond that—no side effects, permissions, rate limits, or irreversible actions. It repeats the obvious fact that it creates a post without any additional behavioral disclosure.

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 a two-word phrase that is not even a complete sentence. It is under-specified, not concise in a useful way. There is no front-loaded information, no structure, and it provides no value beyond the tool name.

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?

With 17 parameters, 3 required, nested objects, and platform-specific limitations (e.g., media constraints, follow-up comment restrictions), the description is completely inadequate. It omits any mention of accountIds, post type, scheduling, or platform-specific behavior. An agent cannot understand what a 'post' entails or what the expected outcome is.

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?

The input schema has 100% description coverage for all 17 parameters, so the schema already documents parameter meanings. The description itself contributes no parameter information, which is acceptable given high schema coverage. Baseline 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 'Create post' states a verb and a generic resource, but it does not specify that it's for social media posting, nor does it differentiate from sibling tools like social_media_posting_edit_post or social_media_posting_delete_post. It is only slightly more informative than the tool name itself, which already includes 'create_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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, required fields, or exclusions. The description provides zero context for tool selection among the many social_media_posting_* siblings.

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