get_insights

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

With no annotations, the description must convey behavioral traits. 'Fetch' implies a read-only operation, but there is no mention of pagination, required parameters beyond level, default behavior, or what the response contains. The single sentence does not meaningfully disclose behavior beyond the action itself.

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 a single, front-loaded sentence with no filler or redundancy. It communicates the core purpose efficiently and is appropriately concise for the information it contains.

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?

This is a complex tool with 10 parameters, no schema descriptions, no annotations, and no output schema. The description only covers the core level parameter and purpose. It omits crucial context like default values, parameter interactions, or expected output, making it only partially adequate for such a 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?

The description maps the 'level' parameter by naming the four allowed values, but the other nine parameters (limit, fields, breakdowns, entity_ids, time_range, date_preset, ad_account_id, time_increment, action_breakdowns) receive no explanation. Since schema coverage is 0%, the description fails to compensate for the majority of parameters.

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 action (Fetch), the resource (insights), and the scope (account, campaign, ad set, or ad). It distinguishes from sibling tools like get_campaign or list_ads, which fetch entities rather than insights.

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 gives clear context that this tool is for fetching insights across different entity levels, implying it's the right choice when metrics are needed. It doesn't explicitly exclude alternatives or mention sibling tools, but the context is unambiguous.

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