export_broadcast_recipients

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds context that it runs a POST that returns data, changes no account records, and may create a short-lived cached result-set, which provides useful behavioral disclosure beyond annotations.

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 moderately concise but includes an emoji and multiple sentences explaining the POST nature and output. It could be tighter without losing clarity, but it is structurally acceptable.

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?

The description lacks output schema and does not explain the subfields of 'body' parameter sufficiently. It only states output is 'CSV including full contact records', leaving unclear what fields are included or how to handle errors. Completeness is minimal.

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% for parameter names/types but the description does not add meaningful explanation for the parameters. For example, it doesn't clarify what 'order', 'search', 'engagement', or 'deliverability' accept. The description adds no value beyond the schema.

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 'Export broadcast recipients' as a CSV, with the verb 'Export' and resource 'broadcast recipients'. It distinguishes from siblings like 'get_broadcast_recipients' by emphasizing CSV output and search/report behavior.

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 implies usage for exporting recipient data as CSV but does not explicitly specify when to use this tool over alternatives like 'get_broadcast_recipients' or 'export_broadcast_metrics'. No when-not or alternative guidance is provided.

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