Insights de contas do Instagram

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

With no annotations, the description must disclose behavior, but it only mentions aggregation and gives examples. It doesn't cover that this is a read-only operation, that certain metrics require timeframe/breakdown, rate limits, or what happens with empty assets. The phrase 'orgânicas' is useful context but insufficient for safe invocation.

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, front-loaded with the core purpose, no filler.

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 tool has 10 parameters and no output schema, so the description should at least hint at return structure or usage caveats. It doesn't mention that groupBy controls output shape, that some metrics need timeframe, or how deltas appear. This leaves the agent under-informed for a relatively complex tool.

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% with detailed parameter descriptions, so the schema already handles parameter semantics. The description adds a few metric-name examples but no additional syntax or relationships beyond what the schema provides.

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 clearly identifies the tool as providing organic metrics for portfolio Instagram accounts, aggregated by period/account, and gives relevant examples. It doesn't use an explicit verb like 'retrieve' but the resource and scope are unambiguous. It does not explicitly distinguish from sibling tools like page_insights or followers_overview, but the focus on organic metrics and aggregation is fairly specific.

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?

No guidance is provided about when to use this tool versus alternatives such as page_insights, followers_overview, or graph_api_get. The description gives no exclusions or prerequisites.

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