Create a LinkedIn image post

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

Discloses that it posts to personal feed and requires prior login. Could be improved by mentioning posting side effects (e.g., immediate publication) or failure scenarios, but adequate given no annotations.

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 sentences, no redundancy. Front-loaded with action and target. Every word is purposeful.

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?

Covers prerequisites and parameter constraints, but does not describe return values (e.g., post ID, success indicator). Given low complexity and no output schema, this is a minor gap.

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?

Adds value beyond schema by specifying mutual exclusivity of 'imagePath' and 'imageUrl', which schema does not enforce. Schema coverage is 100%, so description augments rather than repeats.

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 verb ('publish'), resource ('image with text'), and target ('logged-in user's personal LinkedIn feed'). Distinguishes from sibling 'linkedin_login' by making it a prerequisite.

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 prerequisite ('Requires linkedin_login to have been run first') and parameter constraint ('Provide exactly one of imagePath or imageUrl'). Provides clear guidance for correct invocation.

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