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

Annotations only say readOnlyHint=false / destructiveHint=false, which is ambiguous for a tool that talks to an external network. The description resolves that by stating nothing reaches LinkedIn until commit, and it discloses the uniqueness constraint, the refusal error (comment_commit_blocked / COMMENT_ALREADY_POSTED), and the required non-retry behavior — none of which appear in annotations or schema.

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 sentences, each doing distinct work: what it drafts, that it is unpublished, where the URNs come from, and the refusal/do-not-retry rule. The unpublished-and-review instruction is front-loaded ahead of the edge cases.

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 an output schema present, return values need no explanation; the description instead covers the workflow, the source of each parameter value, the uniqueness rule, and the error path. Nothing an agent needs to invoke this correctly or handle failure is missing.

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 description coverage is 100% and the schema already explains content length, post_urn provenance, and that comment_id turns the draft into a reply. The description restates that post_urn and the reply target come from the finder tools, adding provenance context but no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 ('Draft a LinkedIn comment ... or a reply to a comment on it') and immediately frames the artifact as unpublished, which separates it from commit_comment_draft and update_comment_draft. An agent can identify the tool and its output without opening the schema.

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 the full workflow: write the text here, show the user, then call commit_comment_draft only on agreement. It also names the prerequisite lookup tools (find_posts_to_comment, find_comments_to_reply), the one-comment/one-reply constraint, the exact failure code, and an explicit 'Do not retry' instruction.

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