harvest_get_profile_reactions

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

The description only mentions the requirement for profile/profileId and does not disclose behaviors such as pagination handling, rate limits, or the response structure. With no annotations to fall back on, this leaves security and operational details undisclosed.

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?

The description is a single sentence that front-loads the core function and the key usage constraint. No filler or redundant information.

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?

Given the lack of an output schema, the description does not explain what a response contains (e.g., reaction counts by type, list of reactors). Pagination is implied by the 'page' and 'paginationToken' parameters but not described. The description covers the essential operation but leaves out expected return details.

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?

The input schema already describes all parameters, but the description adds the critical constraint that at least one of profile or profileId is needed, which is not captured by the schema's required fields. This helps the agent select the right parameter combination.

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?

The description clearly states the tool's function: fetching reactions for a LinkedIn profile using either 'profile' or 'profileId'. It distinguishes from sibling tools that target post or comment reactions.

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?

It specifies that at least one of 'profile' or 'profileId' is required, giving a clear precondition. It does not explicitly compare to sibling tools like harvest_get_post_reactions, but the resource name makes the context obvious. No exclusions are mentioned.

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