generate_linkedin_post

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Generate a LinkedIn post' and does not state whether this creates a stored generation, requires any project state, consumes credits, or simply returns a draft. There is no contradiction, but there is also no meaningful behavioral context beyond the verb.

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 front-loaded sentence with no filler or redundant phrasing. It states the action immediately and earns its place by adding the CreatorOS project context.

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 three parameters, zero annotation coverage, and a large sibling set, the description is too sparse to fully orient an agent. The presence of an output schema covers return-value shape, but the description still leaves parameter semantics, usage timing, and side effects unexplained.

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%, and the description does not explain any of the three parameters. It only weakly hints at project_id via 'for a CreatorOS project', leaving topic and tone undefined. This is a significant gap for a tool with two required parameters.

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 verb ('Generate') and the output resource ('a LinkedIn post'), and the platform is enough to distinguish it from sibling tools like generate_youtube_script and generate_instagram_caption. It does not explicitly name an alternative or add much beyond the tool name, so it stops short of a 5.

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 gives no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent can infer from the tool name and sibling list that it is for LinkedIn posts specifically, but the description itself does not help disambiguate or route between the many sibling generation tools.

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