get_ig_account

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

With no annotations, the description carries the full burden of behavioral disclosure. It only lists profile fields and does not state read-only behavior, authentication requirements, or any side effects. The name implies a read operation, but the description never makes this explicit.

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 short, front-loaded phrase with no filler. It could be structured as a full sentence, but it is efficient and every word contributes meaning.

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?

The output schema likely covers return values, but the description still lacks parameter provenance, usage guidance, and sibling differentiation. For a tool with no annotations and a single undocumented parameter, these omissions leave an agent guessing.

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 clarify the ig_user_id parameter: no format, example, or way to obtain it. The parameter name is partially self-explanatory, but the description itself adds no parameter-level meaning.

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 the resource ('Profil Instagram') and the data it exposes (followers, followed accounts, publication count). It is clear enough about what the tool retrieves, but it does not explicitly differentiate it from sibling tools like get_ig_account_insights or find_instagram_account.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that find_instagram_account might be needed to resolve the account ID, nor does it contrast itself with account insights tools.

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