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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds valuable behavior beyond that: the paged Feed return shape (Size, Items, Previous, Next) and paging mechanics, which matter since there is no output schema.

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; the return shape is front-loaded and filtering guidance follows. No filler, though it packs several concepts (return shape, endpoint, filtering, sorting, escape hatch) into a compact block.

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, describing the Feed structure fills a real gap, and filtering/sorting/escape-hatch guidance covers the main call variations. Nothing critical is missing, though error behavior or rate limits are not mentioned.

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 all five parameters are already documented in the schema including examples for sortby and pagesize defaults. The description reinforces equals-style params and the escape hatch but adds little syntax 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 clear verb+resource (list broadcasts) and immediately scopes it as 'text + voice campaigns', plus names the underlying endpoint GET /v1/broadcasts. This distinguishes it crisp from get_broadcast, get_broadcast_details and create_broadcast siblings.

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?

Explains how to filter (equals-style params) and order (sortby), and explicitly routes date-range operators to the textemall_request escape hatch — a concrete when-to-use-an-alternative statement. It does not spell out a when-not-to-use this tool, so 4 rather than 5.

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