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

Annotations already mark readOnlyHint=false and idempotentHint=false, so the mutating nature is known. The description adds useful auth context by saying the action happens 'on behalf of the connected account,' but it does not disclose public visibility, rate limits, or other side effects beyond the post being created.

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 with no filler, opens immediately with the action, and contains exactly the necessary components: action, target, and actor. It earns its place without redundancy.

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?

With full parameter documentation, an output schema, and annotations present, the description provides enough operational context for a straightforward posting tool. The only slight gap is not explicitly routing replies to an existing comment toward reply_comment, but that is more of a usage-guideline concern.

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 parameters are already fully documented. The description does not add parameter-specific meaning beyond identifying the target as a LinkedIn post and the acting account, which is the expected baseline for complete schema coverage.

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 uses a specific verb and target: 'Post a comment on a LinkedIn post,' and names the acting identity ('on behalf of the connected account'). It clearly describes the action, though it does not explicitly distinguish this from the sibling reply_comment beyond the word 'post.'

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 guidance on when to use this tool versus alternatives such as reply_comment, like_post, or send_message. It does not mention exclusions or prerequisites, so the agent must infer usage from the tool name and target.

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