generate_linkedin_post

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

With no annotations, the description carries full burden. It discloses that it generates three variants for engagement, which is a read-like operation. However, it does not mention authentication requirements, rate limits, or any side effects. The output is implied but not structurally documented.

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 that conveys purpose, input source, and output count. It is concise and front-loaded with the key information. Every word is purposeful and nothing is wasted.

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 no output schema, the description explicitly states the output (three LinkedIn post variants), which is sufficient. The tool is simple (two parameters, one required) and the context from siblings helps. It adequately covers what the agent needs to know.

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 100% and both parameters are already described well in the schema. The description adds no additional meaning beyond summarizing the content parameter as 'any content (article, newsletter, notes, etc.)'. Baseline score 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 clearly states the tool generates three LinkedIn post variants from any content to optimize engagement. It uses specific verbs ('generate') and resources ('LinkedIn post variants'), and distinguishes from siblings like publish_linkedin_post or get_linkedin_posts.

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 implies it should be used when you have source content to transform into posts, but does not explicitly state when to use this tool versus alternatives like analyze_linkedin_chat or schedule_linkedin_post. No exclusions or when-not-to-use guidance is provided.

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