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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: newest-first ordering, cursor paging, and that bodies are omitted while name/status/audience/subject/schedule are returned. It says nothing about page size behavior, empty results, or what the cursor looks like.

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?

Two tight sentences, zero filler. The scope and field list come first, and the pointer to the sibling for full bodies is placed last, which is the right ordering.

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 usefully enumerates the returned fields and omits bodies, which is the key completeness need for a list tool. It leaves gaps on filtering by status and pagination mechanics that an agent would otherwise have to infer.

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 0%, so the description must carry parameter meaning; "page through" hints at cursor/limit but gives no defaults or bounds. Most notably the status filter with five enum values is never mentioned, and the required project_id scoping is only implicit in "a project's broadcasts."

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 names a specific verb and resource ("Page through a project's broadcasts") and immediately scopes it against the sibling "get_broadcast" by disclaiming bodies. The agent can distinguish this list tool from get_broadcast without opening either schema.

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?

It explicitly routes the agent to get_broadcast when the HTML body is needed, and the paginated listing framing implies when to use it. It stops short of stating exclusions or mentioning that results can be narrowed by status or how to begin paging.

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