cf_bulk_redirect_upsert

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

Discloses all-or-nothing validation, async addition, and dry_run support beyond what annotations provide. No contradictions with annotations.

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?

Three sentences with no wasted words. Purpose upfront, followed by gating and behavior, then async note.

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?

Covers purpose, gating, validation, dry_run, async. Lacks description of return value or response structure, but overall adequate for a complex bulk operation.

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 coverage is 100%, so description adds little beyond schema. It reinforces the confirm and list_name relationship but no new parameter details.

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 states the tool creates or appends many redirects via a bulk redirect list for site migrations. It distinguishes from siblings like cf_create_redirect (single) and cf_delete_redirect.

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?

Provides explicit gating conditions (destructive env variable and confirm value) and mentions dry_run. Does not explicitly list alternatives, but the context implies when to use single vs bulk tools.

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