List scheduled campaigns

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

With no annotations provided, the description carries the full burden. The verb 'List' implies a read-only operation and 'waiting to run' clarifies the campaign state, but the description does not mention response shape, pagination, or other behaviors. This is minimally adequate for a simple no-parameter list operation.

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 a single, front-loaded sentence with no filler. Every word adds meaning by identifying the operation, the resource, and the relevant state.

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 operation, the description is nearly complete: an agent knows what to expect and how to invoke it. The main gap is the lack of differentiation from gambot_list_campaigns and the absence of any return-format hints, but the tool's low complexity reduces the impact of these omissions.

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 input schema has zero properties, so there are no parameters to document. The baseline for a no-parameter tool is 4, and the description's 'scheduled campaigns waiting to run' effectively defines the implicit selection criteria.

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 uses the specific verb 'List' and identifies a precise resource: scheduled campaigns that are waiting to run. It clearly distinguishes this from the sibling gambot_list_campaigns by narrowing to the scheduled/waiting state.

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 gives no guidance on when to use this tool instead of gambot_list_campaigns or other campaign-related tools. It does not state any exclusions, prerequisites, or alternative conditions, leaving the choice to inference.

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