get_media_insights

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

No annotations provided, so description bears full burden. It discloses that reels return plays while photos don't, but does not mention whether the operation is read-only, required permissions, rate limits, or other side effects. Lacks explicit safety or behavioral context beyond metrics variation.

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 sentences, front-loaded with purpose, no redundant words. Every sentence adds value: first states main function, second adds critical detail about metric variability. Highly efficient.

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 single-parameter tool with output schema (implied), description covers core functionality and key behavior differences. Missing minor details like read-only nature, but overall sufficient for correct usage. Could mention prerequisites or limitations.

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 has one parameter 'media_id' with description 'The media ID from list_recent_media', achieving 100% schema coverage. Description does not add new parameter semantics beyond implying media_id identifies the post/reel, but baseline is 3 due to high coverage.

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?

Description explicitly states 'Get performance metrics for a single post/reel', clearly specifying the verb and resource. It distinguishes from siblings like get_account_insights (account-level) and get_ad_insights (ads) by focusing on individual media, and mentions different metrics for reels vs photos, adding specificity.

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?

Description lists returned metrics and notes variation by media type, but does not explicitly state when to use this tool over alternatives (e.g., for account-level insights use get_account_insights). Usage context is implied but lacks explicit exclusions or recommendations.

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