List Broadcast Clicked Links

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

Annotations include readOnlyHint=true, consistent with the read-only listing behavior. The description adds meaningful behavioral context: return fields, the fact that 'id' is an opaque pagination cursor and not an entity id, and guidance to use pagination for large lists. This goes beyond the annotation and helps the agent interpret results correctly.

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 well-organized with labeled sections (Purpose, Returns, When to use) and no filler. Each sentence contributes useful information, and the most important purpose statement is front-loaded.

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?

There is no output schema, so the description appropriately documents the return fields and pagination semantics. All four parameters are covered by the schema, the read-only behavior is clear from annotations, and the usage guidance is complete enough for an agent to call the tool correctly.

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 the description does not need to repeat parameter definitions. It adds value by explaining how limit/after/before work together for pagination and by clarifying that the returned id is a pagination cursor. Minor gap: it does not separately explain the broadcastId URL alternative, but the schema already covers that.

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 ('List the links clicked in a broadcast') and adds ranking by total clicks. It also explicitly distinguishes itself from get-broadcast by noting 'use this for per-link click data,' so it is clearly differentiated from 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?

Provides concrete when-to-use examples ('what links were clicked in this broadcast?', 'top clicked links') and names the alternative get-broadcast for overall broadcast details. This gives an agent clear routing guidance without ambiguity.

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