List campaigns

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

No annotations are provided, so the description carries the full burden. It only says 'List all broadcast campaigns' and does not disclose whether this is read-only, whether it returns paginated results, what fields are included, or whether it includes scheduled/draft campaigns. The word 'broadcast' adds some scope but not behavioral detail.

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?

One sentence, no filler, and the key scope ('broadcast campaigns') is front-loaded. Every word earns its place.

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 zero-parameter list tool, the description is minimally adequate: it names the resource and scope. However, with no output schema and no annotations, it would benefit from stating whether the result is a list of campaign IDs/names and whether any filtering or pagination applies. The sibling list shows many campaign-related tools, so a bit more differentiation would improve completeness.

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 tool has zero parameters, so there is no parameter semantics burden. The description's mention of 'broadcast campaigns' clarifies the resource scope, which is the only semantic context needed. Baseline 4 for zero params is appropriate.

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 ('List') and resource ('broadcast campaigns') and scopes it to the organization. It is clear enough to distinguish from related tools like gambot_list_scheduled_campaigns and gambot_get_campaign, though it does not explicitly name those 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?

The description implies usage: call this when you need all broadcast campaigns for the organization. It does not explicitly state when to prefer this over gambot_list_scheduled_campaigns or gambot_get_campaign, nor does it mention any exclusions or alternatives.

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