listBulkCallNumbers

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral details beyond that: it returns the current dialing number and explains the semantics of calls_this_cycle vs calls_dispatched. This helps an agent understand the live/stateful nature of the read operation and what the lifetime vs cycle counters mean.

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 core description is front-loaded and compact, with the main purpose stated first and field semantics following in two concise sentences. The trailing '(Tags: Bulk calls)' is minor noise but does not significantly hurt clarity.

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 present, the description does enough by explaining the main return concepts (number pool, current dialing number, calls_this_cycle, calls_dispatched) and their operational meaning. It could be slightly more explicit about the full response shape, but for a simple one-parameter read-only tool this is reasonably complete.

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 only parameter, bulk_call_id, is fully described in the schema ('Id of the bulk call campaign'), giving 100% schema description coverage. The description adds no additional parameter-specific detail, but none is needed given high coverage and a single simple parameter.

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 clearly identifies the resource as the campaign's number pool and adds the distinctive live element of which number is dialing now. It is distinguishable from general tools like listPhoneNumbers and searchPhoneNumbers, though it doesn't explicitly say 'list' or name a sibling to differentiate from. The annotation title 'List campaign number pool' reinforces the action.

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 when the tool is useful by saying calls_this_cycle is the field to watch for the next rotation, giving practical guidance for interpreting results. However, it does not explicitly state when to use this tool over alternatives like listBulkCallLines or getBulkCallLiveStatus, nor does it mention exclusions.

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