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

Annotations declare a non-destructive write, and the description adds non-obvious behavior: if LinkedIn is not connected the tool returns a connect link the agent should hand to the user, and a single post covers both LinkedIn and later Instagram. It stops short of describing auth setup beyond the connect link or error conditions.

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?

Front-loads the core action and format, then conditions (LinkedIn-only, connect-link fallback, Instagram-at-publish). Dense but each clause carries real information; slightly long but no filler.

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?

For a non-idempotent write with no output schema, the description covers the important edge behaviors (connect-link return, single-post model). What it does not cover is post-creation success output, which matters somewhat given no output schema exists.

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%, so the baseline is 3. The description adds value by clarifying the caption/context relationship ('provide either a ready caption or a context for AI to write one'), which is a mutual-exclusion rule the schema descriptions only imply individually.

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 and resource (create a swipeable document post from a PDF) and pins the format and scope: the LinkedIn page-by-page carousel. It clearly distinguishes itself from PDF-less carousel siblings like create_carousel and create_photo_carousel by naming the PDF/LinkedIn constraint.

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?

Gives strong when/when-not context: LinkedIn is the ONLY platform that renders a PDF, and Instagram is normally added at publish time rather than creation. It does not explicitly name alternative sibling tools (e.g. create_carousel) for when a PDF is not the right input, but the platform conditions are clear.

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