Bulk: Generate CSV Template

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

With no annotations, the description carries the burden. It discloses what the tool returns (csv, columns, report), how columns are ordered, and that no CRM-specific behavior is built in. It doesn't explicitly state whether the operation is read-only, but 'Generate' suggests no mutation; still, an explicit safety note would make it 5.

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 concise paragraphs front-load the primary purpose and returning shape, with efficient, non-redundant language. Every sentence provides value (same-config guarantee, ordering detail, output contract).

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 tool with nested config and no output schema, the description hands out the return shape, report semantics, and ordering rule. The schema covers parameters in depth; the description fills the output/behavior gap. No significant missing context.

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 schema descriptions already cover 100% of parameters with detailed semantics (e.g., enum strategies, address_config rules). The description references field configuration but adds no per-parameter semantics beyond the schema. This meets the baseline but doesn't exceed it.

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 names a specific action (generate), a concrete artifact (CSV template), and a distinct output (per-field behavior report). It clearly separates this from sibling bulk_validate and bulk_execute tools by focusing on template generation.

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?

It explains the intended workflow by stating the template uses the same field configuration as validate/execute, implying this should run before those tools. It does not name alternatives or explicit when-not conditions, so not a 5.

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