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

No annotations are provided, so the description carries the full behavioral burden; it declares 'Read-only' and enumerates the metric families returned, which is genuinely useful. It says nothing about cost/latency, result size, pagination, or how the daily series is bounded, which matters for an analytics aggregation tool with a variable date range.

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?

A single front-loaded sentence that opens with the scope and constraint before the metric list, with zero filler. The dense em-dash list of returned sections is efficient, though it packs a lot into one sentence.

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?

With four optional parameters and no output schema, the description does a fair job by listing the returned sections. However, all parameters are optional and the description never states the default date window or behavior when no filters are supplied, leaving a real ambiguity for an agent deciding how to call it.

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 50% — to/from describe only the YYYY-MM-DD format, while search_id and campaign_id are bare. The description compensates by defining search_id as 'one SDR search' and campaign_id as 'one campaign' and by stating they are mutually exclusive, semantics absent from the schema. It does not explain what happens when from/to are omitted.

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?

States a specific verb and resource (outreach analytics over a UTC date range) and enumerates exactly what it returns: totals, rates, daily series, delivery, breakdowns, contacts, enrichment, funnel, per-process rows. This clearly separates it from single-purpose siblings, but it never names an alternative tool, so it stops short of explicit sibling 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?

Gives a clear usage rule: query across Vendo SDR and classic campaigns, or narrow to one search_id or one campaign_id — 'never both', which is an explicit mutual-exclusion constraint the agent would otherwise have to guess. It lacks any statement of when to prefer this over the narrower analytics siblings (e.g. campaign-level analytics tools).

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