get_post_likes

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

With no annotations, the description carries the burden. The words 'List' and 'GET' imply a read-only operation, and the response contents (id/name) are mentioned. However, pagination behavior and the role of the 'after' parameter are not disclosed, which is a meaningful omission given the 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?

The description is one tight sentence with no filler. The endpoint is added parenthetically without disrupting flow, and the core action and outcome are front-loaded.

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?

The tool has a required post_id and optional pagination parameters, and an output schema exists to cover return values. However, the description omits pagination context (what 'after' does) and any authentication notes, leaving some gaps for an agent invoking the tool with more than the default parameters.

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 0%, so the description must compensate. It implicitly identifies post_id via the endpoint '/{post-id}/likes', but it does not explain the optional 'after' and 'limit' parameters. The agent is left to infer their semantics from type and defaults alone.

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 states a specific verb ('List') and resource ('people who liked a post'), and includes the exact endpoint. It clearly distinguishes this from sibling tools like get_post_reactions and get_comment_likes by specifying the post context and the nature of the data (people who liked).

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 explicit guidance is provided on when to use this tool versus alternatives such as get_post_reactions or get_comment_likes. The description only states the action without naming any exclusions or preferred conditions, leaving the selection to inference.

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