get_v2_media_likers

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

No annotations are provided, and the description only says 'get user's likers', implying a read operation but offering no additional behavioral traits like pagination, ordering, rate limits, or response format. The description adds minimal value beyond the tool name.

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 brief (two short lines), but conciseness is undercut by lack of useful information. It could be restructured to front-load the core action and clarify the parameter.

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 no output schema, 0% parameter description coverage, and no annotations, the description is severely incomplete. An agent cannot determine the input semantics, output structure, or how to use this tool effectively.

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%, and the description does not explain the purpose or format of the required 'id' parameter (e.g., is it a media ID?). No value added beyond the schema's basic type.

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 'Get user's likers' and title 'Media Likers', which suggests retrieving users who liked a media, but it's ambiguous whether 'user's' refers to the media owner or the media itself. It does not clearly distinguish from siblings like get_v1_media_likers or get_gql_media_likers.

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 on when to use this tool versus alternatives such as get_v1_media_likers or get_gql_media_likers. The description lacks any context for tool selection.

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