create_social_post

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It states it 'generate[s]' a post but does not reveal side effects, persistence, whether it actually publishes to a platform, or any prerequisites. This is a basic action statement without deeper behavioral context.

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 single sentence with no filler or redundant information. It is front-loaded with the action and subject, making it immediately understandable and appropriately concise.

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?

Although the tool is simple with two parameters and an output schema, the description lacks critical context about the tool's behavior, such as whether it posts to a social network or just returns generated content. It does not clarify the relationship between image and text or any side effects. A bit more detail would make it complete.

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 0% schema description coverage, the description must compensate for explaining parameters. It implicitly addresses 'topic' via 'any topic', but the 'style' parameter is completely ignored, and no additional meaning is added beyond the schema's field names. The description only partially compensates for the lack of parameter documentation.

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 uses the specific verb 'Generate' and identifies the resource as a 'social media post with image and text', which clearly states what the tool does. It is distinguishable from siblings like web_search and create_quote_card by focusing on social posts with both image and text, though not explicitly differentiating them.

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?

No explicit guidance is provided on when to use this tool versus alternatives such as create_quote_card or get_slide_image. The phrase 'for any topic' implies broad usage but does not clarify exclusions or when a different sibling might be more appropriate. This is minimal guidance at best.

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