get_daily_performance

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

With no annotations, the description must disclose behavioral traits. It mentions the default window (7 days) and lists returned metrics, but does not state whether the tool is read-only, requires authentication, or has rate limits. The lack of transparency about side effects or data freshness is a gap.

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 packs essential information: timeframe, metrics, and grouping dimensions. No superfluous 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?

The tool has few parameters and an output schema, so the description could suffice. However, it does not address edge cases (e.g., empty data) or provide context on how metrics are calculated. The output schema likely documents return values, but the description could still be more complete.

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 description covers the 'days' parameter by indicating it sets the 'last N days' window with a default of 7. However, the 'account_id' parameter is not explained at all; the description does not clarify its role or optionality. Given 0% schema coverage, the description partially compensates but remains incomplete.

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 the tool returns daily performance metrics (impressions, clicks, spend, etc.) grouped by date and campaign ID, with a configurable lookback window. However, it does not explicitly differentiate from sibling tool 'get_performance_report', which might serve a similar purpose.

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 no guidance on when to use this tool over alternatives, nor does it mention scenarios where it should not be used. For example, it does not explain how it differs from 'get_performance_report' or when to use 'list_campaigns' instead.

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