get_post_comment_reaction

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to deliver. It doesn't indicate whether this is a read-only operation, what permissions might be required, how results are returned (e.g., pagination, format), or any rate limits. The vague 'Get' verb offers no insight into the tool's behavior beyond its basic function.

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 ('Get post comment Reaction') but suffers from under-specification rather than efficient communication. While it's front-loaded with the core action, it lacks necessary detail to be truly helpful. The single sentence structure is simple but incomplete for a tool that likely requires more context to use effectively.

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 tool's apparent complexity (inferred from sibling tools dealing with reactions, posts, and comments) and the absence of both annotations and an output schema, the description is inadequate. It doesn't explain what the tool returns, how to interpret results, or any behavioral aspects. For a tool that likely interacts with social media data structures, this minimal description leaves critical gaps in understanding.

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 has 0 parameters with 100% coverage, meaning no parameters need documentation. The description appropriately doesn't attempt to explain nonexistent parameters, which aligns with the schema's completeness. This meets the baseline expectation for tools without parameters.

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 'Get post comment Reaction' is a tautology that essentially restates the tool name without adding meaningful clarification. It doesn't specify what kind of reaction is retrieved (e.g., likes, emojis, counts) or whether this is for a specific comment or all comments. While it mentions the resource (post comment reaction), the verb 'Get' is too generic compared to more specific alternatives like 'Retrieve' or 'Fetch' that might better indicate read-only behavior.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a specific post or comment ID), differentiate from sibling tools like 'get_post_reactions' or 'get_profile_reactions', or indicate any contextual constraints. This leaves the agent without direction on appropriate usage scenarios.

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