get_ad_insights

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

With no annotations, the description carries the full burden. It correctly identifies a read-only operation, lists returned metrics, and states a permission requirement. However, it does not disclose potential limitations like rate limits, data freshness, or response pagination, which would be valuable.

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 three short, front-loaded sentences: purpose, returned metrics, permission. Every sentence adds value with no fluff. This is efficient and well-structured.

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 2-parameter tool with an output schema, the description covers the primary action and expected return values. However, it lacks details on edge cases (e.g., no data for period), and the date_preset parameter's meaning is only implied by its enum values, leaving some ambiguity.

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 50% (ad_account_id has format info, date_preset has none). The tool description does not add meaning for either parameter; it does not explain date_preset options or provide context beyond the schema enum. The description misses the opportunity to clarify parameter usage.

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 states the tool retrieves ad performance insights for Instagram/Facebook and lists specific metrics. However, it does not explicitly differentiate from sibling tools like get_account_insights or get_media_insights, so a 4 is appropriate.

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?

The description only mentions the required permission (ads_read) but lacks guidance on when to use this tool versus alternatives, no exclusions or context are provided. This is minimal usage guidance.

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