get_bulk_insights

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

No annotations, so description carries full burden. Discloses aggregation behavior, metrics included, and scope. Implies read-only. Lacks specifics on rate limits or data freshness, but adequate for a read tool.

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 clear paragraphs: statement of purpose followed by bullet-style arg list. Every sentence is informative, no wasted words.

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?

Covers usage well, but lacks return format description. Since no output schema, description could mention the structure returned (e.g., per-account row). Sibling get_insights might compensate but not explicit.

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 coverage 0%, yet description explains all three parameters with allowed values, defaults, and constraints (time_range list, level options, limit_accounts max). Adds significant value over bare schema.

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?

Clearly states the verb 'Get performance insights' and resource 'across all accessible ad accounts in one call.' Distinguishes from sibling get_insights which is presumably per account.

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?

Provides explicit context: uses Meta API accounts not accounts.yaml, and campaign-level not supported. Implies when to use (bulk) and when not (need campaign-level). Could mention alternative like get_insights.

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