manage_broadcasts

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions actions like 'create drafts or scheduled sends' and 'delete,' it doesn't clarify permission requirements, whether deletions are reversible, rate limits, or what happens to associated data. For a multi-action tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is reasonably concise but could be better structured. It front-loads the purpose but mixes actions with examples (e.g., 'list with status filter' alongside 'list'). The final sentence listing actions feels redundant after the earlier examples. Some trimming could improve flow without losing clarity.

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 complex multi-action tool with no annotations and no output schema, the description is insufficient. It doesn't explain how to invoke different actions (e.g., via parameters or separate endpoints), what outputs to expect for stats or clicks, or error conditions. Given the richness of possible operations, more contextual detail is needed.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's actions and scope. This meets expectations for a parameterless tool, though it doesn't explain how actions are selected without parameters.

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 clearly states the tool manages Kit email broadcasts and lists specific actions (list, get, create, update, delete, stats, list_stats, get_clicks), providing a comprehensive overview of its functionality. However, it doesn't explicitly differentiate this broadcast management tool from sibling tools like manage_email_templates or manage_sequences, which prevents a perfect score.

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?

The description lists available actions but provides no guidance on when to use this tool versus alternatives like manage_email_templates for template-related tasks or manage_sequences for sequence management. There's no mention of prerequisites, dependencies, or contextual constraints for selecting among these sibling tools.

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