get_profile_reactions

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It mentions 'Returns cleaned data in TOON format,' which hints at output structure, but doesn't disclose critical traits like rate limits, authentication needs, data freshness, or whether it's a read-only operation. For a tool with 6 parameters and no annotations, this is inadequate.

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 extremely concise—two sentences that directly state the tool's function and output format. Every word earns its place with no redundancy or fluff, making it easy to parse quickly.

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 6 parameters, no annotations, and no output schema, the description is insufficient. It doesn't cover key aspects like error handling, data limits (beyond max_items default), or what 'TOON format' entails. For a data-fetching tool with complexity, more context is needed to guide effective use.

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%, so parameters are well-documented in the schema. The description adds no additional parameter semantics beyond implying data retrieval and cleaning. It doesn't explain trade-offs (e.g., profile vs. profileId for speed) or interactions (e.g., paginationToken usage), but the schema provides a solid baseline.

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 action ('Get reactions') and resource ('from a LinkedIn profile'), distinguishing it from siblings like get_profile or get_post_reactions. However, it doesn't explicitly differentiate from get_post_reactions (which targets posts rather than profiles), leaving some ambiguity about scope.

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?

No guidance is provided on when to use this tool versus alternatives like get_profile (which might return general profile data) or get_post_reactions (for reactions on posts). The description lacks context about prerequisites, such as needing a valid LinkedIn URL or ID, or when pagination is necessary.

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