aaddyy_linkedin_post_generator

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

No annotations are provided, so the description carries the burden, and it does disclose one real behavioral trait: the ~50 credit cost. It also reveals that output includes both text and an image, which is useful. But it says nothing about auth, latency, failure modes, or what happens when optional fields like logoFile are omitted.

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 short sentences plus a parenthetical cost note – front-loaded with the core verb and resource. The middle clause is mild marketing filler, but the structure is efficient overall.

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?

Five undocumented parameters, no annotations, no output schema, and no explanation of the text-plus-image return. For a generation tool with this many free-form inputs, the description leaves the agent guessing which fields matter and what the output looks like.

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 description coverage is 0% across 5 parameters (logoFile, postGoal, postIdea, websiteUrl, logoPosition), and the description mentions none of them. 'Brand-aware content' only loosely hints at logoFile/websiteUrl. With zero enum and zero required params, the agent gets no signal on which fields actually drive output quality.

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?

States a specific verb (generate) and resource (LinkedIn posts) plus the added image component, which distinguishes it from aaddyy_instagram_post_generator and aaddyy_thread_generator by platform. Loses a point for not routing explicitly to those siblings.

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?

Marketing copy ('Perfect for building your professional presence') signals intent but gives no when-to-use vs siblings, no prerequisites, and no indication of what inputs are needed. Nothing tells the agent when not to pick this over aaddyy_article_generator or aaddyy_caption_generator.

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