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

Goes well beyond the annotations: public immediately, irreversible ('cannot edit or delete it afterwards'), counts against a 5/day allowance, and requires user confirmation. These are exactly the safety-critical traits an agent needs before calling a destructive, open-world write tool.

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 constraint before enumerating optional capabilities, which is the right order. The long enumeration of optional features adds some density but each item maps to a real parameter, so little 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?

Covers irreversibility, confirmation, rate limits, and key options for a 10-parameter open-world mutation with no output schema. It does not say what a successful call returns (e.g. the new post id/URL), which an agent may need for follow-up calls, but otherwise it is complete.

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 each parameter is already documented in the schema; the description's list of optional features (images, repost, mentions, job card, company page, audience) largely restates what the schema covers. Baseline 3 is appropriate since the schema carries the semantic load.

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 ('Publish ONE post on your own LinkedIn profile, now') with scope that separates it from comment_on_post, repost, campaign/post-target tooling, and scheduled variants. The 'ONE' and 'own profile' qualifiers further distinguish it from bulk or third-party posting.

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 clear when-to-use context (immediate publishing) and a critical precondition ('show the user the exact text and get a yes first'), plus the 5-a-day constraint. It does not explicitly name sibling alternatives (e.g. scheduled posting via add_post_targets), so routing is implied rather than spelled out.

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