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

Annotations are absent, so the description must carry the burden of behavioral disclosure. It only states the billing per call and implicitly that it's a GET request, but does not explain pagination (the 'start' parameter), response format, or whether any rate limits apply. The description is silent on these behavioral aspects.

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, consisting of two short sentences. While it is not bloated, it lacks substantive detail. It does include useful billing information, but the brevity comes at the cost of missing important context. It is efficient but under-informative.

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 there is no output schema and only two parameters, the description should explain what the response contains, how pagination works, and any dependencies on other endpoints. None of this is covered. The tool appears simple, but the lack of return-value details and parameter usage makes it incomplete for a user to invoke correctly without external knowledge.

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 50% (only 'urn' has a description). The description does not add any parameter semantics beyond what is in the schema. The 'start' parameter is undocumented in both the schema and description, leaving a gap that a good description should fill. It does not clarify how 'start' is used for pagination or offsets.

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 article reactions') and specifies the resource scope ('Group: articles'). This distinguishes it from other article-related tools like get_api_v1_articles_all and get_api_v1_articles_article_info, though it could be confused with reactions on other entities, the 'Group: articles' qualifier resolves that.

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_api_v1_posts_likes or get_api_v1_profile_reactions. There is no mention of prerequisites, such as needing to obtain the URN from the articles info endpoint, even though the parameter schema hints at this. The description offers no decision context.

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