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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the return shape (comment text, commenter profile, timestamp) and a non-obvious identifier hazard about ugcPost/share URLs.

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?

Three sentences, front-loaded with the purpose, then inputs, then returns, then the edge-case caveat. Every sentence carries distinct information and nothing is repeated from the schema.

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 no output schema, the description helpfully states what is returned, and the cursor/pagination parameter is documented in the schema. The remaining gap is disambiguation from linkedin_get_nested_comments, which an agent choosing among comment-related siblings would want.

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, but the description adds meaning the schema does not: it explains the provenance of activityUrn (from linkedin_get_person_posts) and warns that the number inside a ugcPost/share URL is not an activity number. That materially reduces misuse of the identifier parameter.

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+resource ('Get comments on a LinkedIn post') and names the source tool for the primary identifier, so an agent can tell it apart from most siblings. However, the close sibling linkedin_get_nested_comments is never mentioned, leaving ambiguity about top-level vs. nested reply comments.

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 explicit input-selection guidance: pass activityUrn from linkedin_get_person_posts, or fall back to postUrl when the URN is unavailable. It also warns against constructing an activity URN from ugcPost/share URLs, which is genuinely actionable. It does not, though, say when to prefer this tool over linkedin_get_nested_comments.

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