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

No annotations are provided, so the description must carry the behavioral burden; it does state 'Read-only', which is important for an analytics retrieval tool. However, it does not disclose permissions, rate limits, data freshness, or response structure, leaving material behavioral context unstated.

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?

Three short sentences with the KPI scope front-loaded, followed by the read-only note and the sibling routing. The metric list is necessary return-shape information and nothing is redundant.

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 scope, metrics returned, optional date range, read-only nature, and the main alternative for combined reporting, which is enough to call it without an output schema. It is not fully complete because it omits pagination/freshness and does not clarify the totals-vs-per-campaign response shape.

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%: both optional from/to parameters already have YYYY-MM-DD descriptions. The description reinforces that the date range is optional but adds no format, default, or interaction details beyond the schema.

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 states a specific read operation over campaign KPIs, enumerating workspace totals and per-campaign performance with an optional date range. It names one sibling alternative (SDR analytics for combined SDR+campaigns), but it does not explicitly route agents away from per-campaign or per-channel analytics siblings such as campaign email/LinkedIn/phone stats.

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?

It gives a clear usage condition for the date range and explicitly redirects combined SDR+campaign reporting to the SDR analytics tool. It stops short of when-not guidance against other campaign analytics siblings, so an agent may still need to infer which tool to pick for channel-level stats.

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