roasr_metrics_campaigns

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully discloses that results are sorted by spend, that reach/frequency are Meta-only and null elsewhere, and that windows earlier than dataSince return empty. However, it does not mention pagination, auth, or output format, so it is not fully transparent.

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 high information density. The description front-loads the core purpose and then adds key behavioral caveats without verbose explanation.

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 no annotations and no output schema, the description covers primary functionality, sorting, platform-specific nulls, and empty-window behavior. It lacks explicit sibling differentiation but is otherwise reasonably complete for a 7-parameter 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?

Schema coverage is 100% for all 7 parameters. The description adds the important dataSince context, which is not in the schema, clarifying behavior of date windows. It also reinforces the 'level' parameter's meaning (campaign/adset), though this is already in the schema. This extra semantics elevates it above baseline.

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 explicitly states the tool returns per-campaign or per-adset metrics and KPIs for a date window, with a list of example metrics and sorting by spend. This is a specific verb+resource combination that clearly distinguishes it from sibling metrics tools by granularity and ordering behavior.

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?

No guidance is given on when to use this tool versus alternatives like roasr_metrics_summary, roasr_metrics_daily, or roasr_metrics_breakdown. The description implies campaign/adset-level analysis but does not mention exclusions or alternative use cases.

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