instagram_unlike_post

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It simply states the action with no details about side effects, required permissions, error conditions, or whether the operation is reversible. For a mutation tool, this is insufficient.

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 very short (one sentence), which is concise but lacks substance. It is front-loaded with the core action, but every sentence should earn its place; here, the sentence is too minimal to provide adequate information.

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 the complexity of the sibling tools (many Instagram actions) and the lack of annotations, the description is incomplete. It does not explain return values despite an output schema existing, and it omits important context about when the tool is applicable.

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 single parameter 'media_id_or_url'. The parameter type is 'string', but the description gives no hints about acceptable formats (e.g., numeric ID vs. full URL), leaving the agent to guess.

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 name 'instagram_unlike_post' clearly indicates the action (unlike) and resource (post). The description 'Remove a like from a post' is a specific verb+resource, and it directly contrasts with the sibling tool 'instagram_like_post', making differentiation unambiguous.

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?

The description provides no explicit guidance on when to use this tool or when to avoid it. It implicitly contrasts with 'instagram_like_post', but lacks context about prerequisites (e.g., must have previously liked the post) or alternatives.

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