unlike_media

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

Discloses that this is a write operation and specifies the required permission. With no annotations provided, the description adequately informs the agent of the behavioral impact (modification) and authorization needs.

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 concise sentences with essential information (action, resource, operation type, permission). No filler, front-loaded for quick understanding.

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 tool with one parameter and an output schema (though details not shown), the description is sufficient. It covers purpose, operation type, and permission. Could mention return value but not critical.

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 100% and the parameter description 'Media ID to unlike' is clear. The tool description does not add further semantics beyond what the schema provides, so baseline score of 3 applies.

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?

Description clearly states the action ('Unlike') and the resource ('a post or reel'). It directly distinguishes from the sibling tool 'like_media' by being the opposite operation.

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?

Explicitly notes it is a write operation and requires the 'instagram_manage_engagement' permission, providing clear context for when to use. However, it does not mention alternatives or when not to use, though the inverse nature with like_media is implied.

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