instagram_tagged

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

Annotations cover safety (readOnlyHint, openWorldHint), so the bar is lower, and the description still adds real value: it discloses that only public posts are returned, that the tagged posts come from other accounts, and the 1-credit cost. It does not discuss pagination behavior, which the cursor param implies but the description never confirms.

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 short sentences plus a cost line, front-loaded with the core purpose and zero filler. Every sentence carries 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?

For a read-only, three-parameter tool with no output schema, the description adequately covers what is returned and the cost. The remaining gap is that it never states that user_id or username must be supplied, leaving the zero-required-parameters schema unexplained.

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 100%, so the baseline is 3; the description adds nothing about cursor, user_id, or username. Notably, the schema marks no parameters as required even though one of user_id/username is logically needed, and the description does not resolve that ambiguity.

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 ('Get posts an account is tagged in') and clarifies the scope as posts by other accounts that tag this account, which distinguishes it conceptually from instagram_posts/instagram_media. It does not name those siblings explicitly, but the resource is specific enough to select correctly.

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?

Usage is implied by the scope clause ('Public posts by other accounts that tag this account'), which hints at when this differs from a normal posts feed. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the routing.

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