See Instagram posts

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds that posts and reels are both included, which is useful content-type context. However, it says nothing about recency window, result limits, pagination, or whether a brand must be selected first.

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?

A single short sentence with no filler, front-loading the action and the resource. Every word earns its place.

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 read-only tool with annotations and no output schema, the description covers what is returned (posts and reels). It is still thin on operational detail such as recency bounds, volume, and brand binding, which an agent would need to call it confidently.

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?

With 0 defined parameters, the baseline is 4, but the description refers to 'a brand's' posts while the schema defines no brand parameter (additionalProperties: true). That mismatch mildly muddies how the tool is scoped and leaves the brand selector unspecified.

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?

States a specific verb+resource ('See a brand's recent Instagram posts and reels'), naming the content types returned. It does not explicitly differentiate from siblings like get_brand_ads or get_brand_stats, but no sibling covers Instagram content, so it is reasonably distinguishable.

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 when-to-use guidance, no prerequisites, and no alternatives named (e.g., when to use this vs get_brand_ads or research_tiktok_ads). The word 'recent' implies scope but does not tell the agent when this tool is the right choice.

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