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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that: it discloses the ~1 minute data freshness lag, defines rates as fractions of sent_count, and warns that rates are null before anything is sent — all behaviors an agent could otherwise get wrong when interpreting results.

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?

One dense sentence covers the metric list first, then the rate semantics, then the freshness caveat — well front-loaded with no filler. The metric enumeration is long but every item is distinct information rather than repetition.

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?

For a one-parameter, read-only tool with no output schema, the description carries the return-value burden well by enumerating totals, per-day series, rates, and per-link clicks. The only material gap is that it never says what broadcast_id refers to, which matters because the schema is silent on 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 description coverage is 0%: the single parameter broadcast_id has no description in the schema, and the description never mentions it or says which identifier it expects. With one undocumented parameter, the description should compensate, and it does not.

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?

"How a broadcast did" pins the resource (a broadcast) and the sentence enumerates the exact metrics returned, so an agent knows this is a per-broadcast performance read rather than a raw event listing. It never uses an explicit verb like "get" or "return", but the resource and scope are unambiguous and distinguish it from get_campaign_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?

There is no when-to-use guidance and no mention of alternatives such as get_broadcast (settings/metadata) or list_email_events (raw events). The agent must infer from the name alone that this is the aggregate-metrics tool; the only implicit hint is the word "broadcast" versus sibling campaign tools.

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