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

With no annotations, the description carries the full burden and does well: it discloses the freshness skip, that enrichment is limited to never-seen people up to max_enrich, and an explicit cost model (2 credits/post, 3/person, cached posts free). It omits permission/auth requirements and does not describe the return shape, which matters because there is no output 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?

Three dense sentences, front-loaded with the what, then the freshness/enrichment mechanics, then the cost. Every clause carries decision-relevant information (scope, cost, caching) with 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?

For a 6-parameter aggregation tool with no annotations and no output schema, the description covers behavior, caching, and billing well. The remaining gaps are the return shape (what fields a deduped engager carries) and what happens when profile_id and collection_id are both or neither supplied.

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 real meaning by tying max_enrich to the enrichment pass and its 3-credit cost, and by explaining that freshness_days drives both skipping and free cached reads. It leaves the profile_id/collection_id relationship (mutual exclusivity, behavior if neither is given) unexplained.

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 ('Return the consolidated, deduped people who reacted to or commented on a SET of posts') and immediately scopes it to two input modes, profile_id or collection_id. The emphasis on SET plus 'consolidated, deduped' distinguishes it from the single-post siblings like linkedin_post_reactions and linkedin_post_comments without naming them.

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 clear selection context: use profile_id for one tracked profile's stored posts or collection_id for a collection's posts, and it explains the freshness gate that governs whether a call does work. It does not explicitly say the two ids are mutually exclusive or when to prefer this over get_post_engagers_by_company, so it stops short of full when/when-not guidance.

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