Verifies whether a given Instagram user follows @in.yogeshwar by checking their User ID, enabling follow-gated access and audience validation.
Check whether an Instagram user follows @in.yogeshwar (Follower Verification).
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | Instagram User ID (IGSID). |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Check' implies a read-style operation and the target account is named, but the description does not disclose authentication requirements, rate limits, error behavior, or return semantics, leaving important behavioral traits undocumented.
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 a single, front-loaded sentence with no redundant text. Every part of the sentence contributes to identifying the operation and the target account.
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 one-parameter check tool, the core purpose is clear. However, with no annotations and no output schema, the description does not state the return shape or edge-case behavior, so an agent must infer what a successful response looks like.
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?
The schema has 100% description coverage for the single user_id parameter, including that it is an Instagram User ID (IGSID). The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline score of 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 states a specific verb and resource: checking whether an Instagram user follows a named account, @in.yogeshwar. This is clearly distinct from the sibling profile-getting and publishing tools because it verifies a follow relationship rather than returning profile/content data.
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 parenthetical 'Follower Verification' implies the use case, but the description does not explicitly state when to use the tool, prerequisites, or exclusions. The sibling list has no direct alternative for this check, so the missing alternative guidance is less harmful, but usage remains implied rather than specified.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.