like_media

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

With no annotations, it carries the burden. It states required permission, but lacks details on side effects (e.g., behavior if already liked, rate limits). Some transparency but incomplete.

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?

Two efficient sentences without wasted words. The bold line emphasizes the key constraint (write operation and permission), front-loaded 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?

For a simple single-parameter tool with an output schema, it covers purpose, permission, and source of parameter. Minor gap: what happens if already liked? Still mostly complete.

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?

One parameter with schema coverage 100%, and its description explains origin (from list_recent_media). The tool description adds no additional parameter meaning, so baseline 3 is appropriate.

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 'Like a post or reel' on the user's account, which is specific and distinguishes it from siblings like 'unlike_media' or 'like_comment'.

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?

It explicitly mentions it is a WRITE operation and requires a specific permission, but does not provide when-to-use vs alternatives (e.g., unlike_media) or any exclusions.

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