List campaigns

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

Annotations already declare readOnlyHint and openWorldHint, and the description's 'List' wording is consistent. It adds useful context beyond the annotations by specifying the scope ('outbound campaigns') and the field content ('id and name'), though it does not describe ordering, pagination, or response envelope details.

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 short sentences with the action and result front-loaded, and the instruction to 'Start here' earns its place as workflow guidance. There is no filler, repetition, or unnecessary detail.

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 parameterless list tool with readOnly/openWorld annotations, the description adequately covers purpose, scope, returned fields, and how it fits into the workflow. It does not document the exact output schema, but the named fields ('id and name') and the simple nature of the tool make this a minor gap.

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 parameters and 100% schema description coverage, so there is nothing for the description to clarify. The description implies a parameterless call by saying 'List the outbound campaigns', and no ambiguity exists.

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 a specific verb ('List') and identifies both the resource ('outbound campaigns on the ICTContact / ICTDialer server') and the returned fields ('id and name'). The phrase 'Start here to find a campaign id' clearly separates this from the sibling tools, which operate on individual campaigns.

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 explicitly frames this tool as the entry point for discovering campaign IDs, which implies it should be used before campaign_summary, campaign_status, or campaign_result. It does not explicitly name those alternatives or state when not to use it, but the 'Start here' guidance provides clear context.

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