get_campaign_performance

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

With no annotations, the description carries the burden of behavioral disclosure, and it does disclose one non-obvious trait: only the optimization event of each ad set counts as a 'Result'. However, it does not cover other behavioral aspects like data freshness, permissions, pagination, or response details, leaving the disclosure partial.

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 sentences with no filler, placing the core purpose first and a valuable caveat second. Every sentence earns its place.

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?

There is no output schema and the description does not enumerate the KPI fields returned, so an agent cannot tell whether the tool provides metrics like spend, clicks, or conversions beyond 'Result'. The missing usage guidance and absent response details make the definition incomplete for a reporting 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?

The input schema already documents all six parameters with 100% coverage, so the baseline is 3. The description adds no specific parameter clarification beyond the Result metric definition, but it does not need to compensate for missing schema documentation.

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 verb 'Get' plus 'performance KPIs for campaigns' identifies a clear resource and action, and the note about Ads Manager optimization events adds useful KPI definition. It does not explicitly contrast with siblings like get_creative_performance or get_campaigns, so it stops short of full differentiation.

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 explicit guidance on when to choose this tool over alternatives such as get_creative_performance or get_budget_status. The description focuses on behavior and result definition rather than use cases, prerequisites, or exclusions.

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