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

Annotations already cover safety (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds genuinely new context beyond those fields: the call 'counts against the imports quota', which is a billing/limit trait not available in annotations. It stops short of noting rate limits or pagination, so 4 rather than 5.

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 compact sentences with zero filler. The core action leads, followed by parameter guidance, the sibling disambiguation, and the quota caveat in descending order of importance.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. With purpose, parameters, alternative routing, and quota cost all addressed, nothing an agent needs to select and invoke the tool correctly 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 coverage is 100%, so the baseline is 3. The description adds guidance the schema does not convey: 'Pass the full post URL or slug' clarifies the accepted format, and 'Set liked=true and/or comments=true' communicates that the flags are independent and combinable, which is a usage rule rather than a restatement of field types.

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 ('Fetch likers and/or commenters for a LinkedIn post') and explicitly delimits scope to a single post you have the URL for. It also names the sibling it is not (scrape_my_posts), so an agent can distinguish it without opening either 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 an explicit when-to-use condition ('one post you have the URL of') and an explicit alternative with its own condition ('for the account's own recent posts use scrape_my_posts'). It also discloses a cost constraint (imports quota) that affects selection.

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