get_insights

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read via 'Get' but says nothing about whether this is read-only, what date range defaults apply, how 'limit' paginates, or how breakdowns affect the result shape — all things an agent needs for a 6-parameter analytics call.

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?

It is a single short sentence with no wasted words and the tool's scope is front-loaded. But terseness here is under-specification rather than efficiency, so it only reaches the minimum viable level.

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?

An output schema exists so return values need not be explained, which helps. Still, a six-parameter tool with zero annotation coverage, zero schema descriptions, and no usage guidance is left materially incomplete for correct invocation.

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 0% across six parameters, so the description must compensate and largely does not. The phrase 'account or a specific campaign' loosely hints at ad_account_id vs. campaign_id, but level, limit, breakdowns, and date_preset are entirely unexplained.

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 names a verb ('get'), a resource ('insights') and a scope ('account or a specific campaign'), which is better than a tautology. However, it does not differentiate itself from the sibling get_account_insights, which sounds like it covers exactly the 'account' half of the scope, leaving the agent unsure which tool to pick.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. Given the closely overlapping sibling get_account_insights and the analytics siblings (compare_performance, analyze_campaign), the agent is left to guess which tool serves which need.

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