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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' is redundant; however, the description adds a genuinely non-obvious semantic caveat: 'Sent counts reflect messages attempted, not confirmed deliveries.' That prevents misreading of the returned numbers and is not derivable from any structured field.

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: payload definition first, safety class second, interpretation caveat last. Every sentence carries information and nothing is padded or repeated.

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?

There is no output schema, so the description must characterize returns — and it does, naming both the status breakdown and per-block sent/clicked counts. The 'attempted vs confirmed' caveat covers the main ambiguity; only details like pagination or metric units are left unstated, which is minor for an analytics read.

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 100%, so broadcastId, applicationId, startDate, and endDate are all fully documented (including per-key default behavior for applicationId). The description only restates the existence of an optional date window, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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: 'Return engagement analytics for a broadcast', then enumerates the payload shape (delivery breakdown by status, per-message-block sent/clicked counts). This distinguishes it from siblings like get_broadcast_details (metadata) and get_flow_analytics (flow-wide), though it never names those alternatives explicitly.

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?

'over an optional date window' implies the startDate/endDate use case and 'Read-only' tells the agent the operation class, but there is no explicit when-to-use guidance or steering toward get_flow_analytics/get_funnel_analytics for other analytical views. Usage is implied rather than directed.

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