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

With no annotations, the description carries the disclosure burden and does so meaningfully: it labels the data as 'live from Meta,' specifies that results are media eligible for promotion, and names the returned fields including a pagination cursor. It stops short of stating side-effect/auth/error behavior, but 'List' and the return-value detail make the read-only nature clear.

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?

Three focused sentences with the main purpose front-loaded. The detail on return fields and pagination is valuable because there is no output schema, and no sentence is redundant with the input schema.

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?

Given no output schema or annotations, the description includes a full return-field inventory and pagination cursor, plus a clear prerequisite call and sourcing instructions for ig_account_id. An agent can understand what to expect and what to supply.

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?

All 4 parameters are already documented in the schema (100% coverage), so the description does not need to re-explain them. It adds workflow context by pointing to adsap_list_meta_assets for sourcing ig_account_id, but otherwise the schema carries the parameter 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?

States a precise action ('List an Instagram account's recent media/posts') and enumerates the content types (posts, reels, stories). It also distinguishes itself from the sibling list_meta_assets by framing this as the follow-up step for selecting promotable organic content.

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?

Explicitly tells the agent to call this after adsap_list_meta_assets (asset_type:"instagram_accounts") and gives the purpose: picking a post to boost or referencing organic content. It does not list when-not-to-use cases, but the sequencing is strong enough to guide correct invocation.

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