Get Campaign Insights

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a list of returned metrics (impressions, clicks, spend, etc.) but does not disclose other behavioral details like pagination, date range handling, or potential rate limits. This adds some value but not extensive transparency.

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 sentence that front-loads the primary action and follows with a concise list of example metrics. No redundant or verbose wording is present.

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 tool has 8 parameters fully documented in the schema, annotations covering safety, and no output schema. The description gives a high-level sense of return metrics but does not elaborate on response structure or pagination. Given the schema and annotations, this is adequately complete for a read-only insights 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?

All 8 parameters have schema descriptions covering 100%, so the schema provides full parameter semantics. The description itself does not add meaning beyond the schema, so the baseline score of 3 is appropriate.

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 for a specific campaign by ID', using a specific verb and resource. It distinguishes itself from sibling tools like get_account_insights, get_adset_insights, and get_ad_insights by specifying the campaign level.

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 implies this tool is for a specific campaign by ID, providing clear context that it is not for account-level or list operations. However, it does not explicitly mention alternatives or exclusions, such as 'use get_account_insights for account-level data'.

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