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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only that the response includes statistics and scheduling information, which is output content rather than behavioral traits; no auth, rate-limit, or freshness context is offered.

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 tight sentences with no waste; the core action is front-loaded and the return-field list is informative rather than padded. It is appropriately sized for a one-parameter retrieval tool.

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 no output schema, the description carries the burden of describing return values and does name the key metrics and scheduling info, which is good. The gap is sibling disambiguation from meisa_get_broadcast_analytics, which is never addressed despite heavy overlap in the described data.

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% and the single parameter is fully documented with a UUID format hint. The description's 'by UUID' simply restates the schema, so the baseline 3 applies when the schema does all the work.

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 verb and resource ('Retrieve the full details and delivery statistics of a single Meisa broadcast by UUID') and the word 'single' signals it is not a list operation. However, it does not differentiate from the very close sibling meisa_get_broadcast_analytics, which the described stats fields (open/click/bounce rate) would equally suggest.

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?

'Use this when the user asks about results or stats for a specific campaign' gives an implied usage context. But it provides no when-not and, critically, does not tell the agent when to choose this over meisa_get_broadcast_analytics or meisa_list_broadcasts, leaving the highest-risk routing decision to inference.

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