social_post_creator_generate_social_image_action

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

No annotations provided. The description mentions Gemini AI and LinkedIn optimization but does not disclose behavioral details like return format (URL vs binary), rate limits, or whether it is destructive. With no annotations, the description carries the full burden and is insufficient.

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?

Two efficient sentences. First sentence covers features, second covers usage context. No fluff.

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?

Adequately covers the action for a simple image generation tool given high schema coverage. However, lacks explicit mention of return format (but output_variable_name parameter implies URL). Could be more 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?

Schema coverage is 88%. Description adds value by explaining prompt/topic priority (prompt takes precedence) and that image_aspect_ratio 'takes up more feed space on mobile'. These additions justify a score above baseline 3.

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?

Clearly states it generates LinkedIn-optimized images using Gemini, lists 4 visual styles and 2 aspect ratios, and differentiates from generic image generation tools like 'generate_image'.

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?

Explicitly states it can be used as a standalone action or part of the Social Post Creator pipeline. Does not provide explicit when-not-to-use or alternatives, but the context implies it's for LinkedIn social images.

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