get_bulk_insights

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

No annotations are provided, so the description must compensate. It discloses that the tool aggregates spend, impressions, clicks, conversions, ROAS and uses accounts from Meta API. It also mentions the limitation on campaign-level. However, it does not state whether this is a read-only operation or any safety or rate-limit considerations.

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 5 sentences, front-loaded with the core purpose, followed by aggregated metrics, data source note, and a clear Args block. Every sentence adds value, no redundancy.

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?

The description covers inputs and limitations but omits output details. There is no output schema, so the agent has no idea what the response structure looks like. It also does not mention pagination or behavior when limit_accounts is exceeded.

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 input schema has no descriptions for parameters and 0% coverage. The description adds meaning: it explains the time_range string options, clarifies that level only supports 'account', and defines limit_accounts as max accounts with default 20. This compensates well for the lack of schema descriptions.

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 'Get performance insights across all accessible ad accounts in one call.' It specifies the verb 'Get', resource 'performance insights', and scope 'across all accessible ad accounts'. This distinguishes it from siblings like get_insights, which is likely for a single 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?

The description provides context on when to use this tool (for bulk insights across accounts) and notes that it uses accounts from the Meta API, not accounts.yaml. It explicitly states campaign-level bulk is not supported. It does not name an alternative tool, but the context is clear enough.

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