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

Annotations only cover the safety profile (readOnly=false, destructive=false, openWorld=true); the description adds genuinely useful behavior beyond that: immediate publication, platform-specific length caps, the hidden-comment restriction, the brandReplied side effect on the parent comment, and the LinkedIn URN encoding quirk.

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?

Four short sentences; the core action is front-loaded, then constraints, side effects, and the platform-specific gotcha follow in descending order of importance. 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?

No output schema exists, and the description compensates by disclosing the success side effect (brandReplied=true) and the key failure mode (hidden comments), so an agent has everything needed to call this correctly.

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 baseline is 3, but the description adds real meaning: per-platform character limits for message and the instruction to pass a raw, non-URL-encoded URN for platformCommentId on LinkedIn — details absent from the schema.

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 ('Post a public reply to a comment') plus the scope ('on its originating platform'), which cleanly distinguishes it from siblings like create_post, edit_post, and list_comment_replies.

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 a clear usage condition: reply to an existing comment, with an explicit exclusion ('Cannot reply to hidden comments'). It does not name alternatives (e.g., list_comment_replies) or state what to do when replying is impossible, so it stops short of full routing guidance.

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