Prepare Campaign Creator Selection

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is mostly covered. The description adds a useful 100-item cap and the review-before-mutation intent. It does not disclose whether calling this overwrites an existing prepared selection, where the review state lives, or what side effect occurs for an operation that is non-readonly.

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, front-loaded with the action and item limit. There is no filler, and the key usage cue about narrowing before copy or removal is placed immediately after the core action.

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?

The tool has two required parameters, a nested filter object with six fields and enums, 0% schema description coverage, no output schema, and a non-readonly annotation. The description covers only the high-level action and a cap, leaving the filter behavior, campaign scoping, return/selection identity, and side-effect semantics undocumented.

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 0%, and the description never explains campaign_id or any of the nested filter fields such as workflow_filter, source_type, platform, or search. 'matching creator IDs' implies filter semantics, but it does not add meaning beyond the bare schema key names.

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 action and resource: saving up to 100 matching creator IDs for review. The phrase 'before copy or removal' helps distinguish it from sibling mutation tools like copy_campaign_creators and remove_campaign_creators. It is slightly unclear whether the selection is persisted or just prepared, but the core purpose is understandable.

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?

'before copy or removal' and 'Narrow larger selections' imply when to use the tool: as a precursor to bulk copy/removal and when a selection is too broad. However, it does not name alternatives explicitly, nor does it state when not to use it versus list_campaign_creators, search_creators, or save_search_results_to_campaign.

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