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

Read-only safety is already fully declared by readOnlyHint=true and openWorldHint=false, so the description adds nothing there. It discloses no behavior beyond that: not which platforms are covered, what the default time window or limit is, or how the 19 optional filters interact — all of which matter for a read with this many knobs.

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 single short sentence is technically concise but under-specified rather than efficient; brevity here costs the agent nearly all actionable information. There is no front-loaded statement of what the tool returns or how filters apply.

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 19 undocumented optional parameters, no schema descriptions, and only a readOnly annotation to lean on, the description is far too thin to call this tool correctly. The existence of an output schema excuses explaining return values but not the input contract or the tool's role among the many overview siblings.

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?

With 19 parameters at 0% schema description coverage, the description carries the full burden of explaining them, and it explains none. Parameters such as range_preset, activity_only, limit, sort_by, and the distinction between date_from/date_to and days are left entirely undefined.

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 'Account overview for insights context' essentially restates the tool name (meta_insights_get_overview), adding only a vague notion of 'context'. It gives no indication of what data the overview contains or how it differs from siblings like overview_get_account, meta_insights_compare_platforms, or meta_ads_get_summary.

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 guidance on when to use this tool versus the many overlapping siblings (overview_get_account, google_ads_get_summary, meta_ads_get_summary, meta_insights_compare_platforms). No prerequisites, no exclusions, not even an implied selection criterion beyond 'insights context'.

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