subscriber_bulk_import

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

Discloses key behaviors: import is a write operation, conflict handling, dry run validation without writing, and row caps. Missing details on authentication or error handling for malformed CSV beyond blank/comment lines, but adequate given no 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?

Concise and well-structured: a brief header, bulleted CSV format rules, and a clear parameter list. Every sentence adds value, no redundancy.

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 all necessary aspects for an agent: input format, parameters, conflict handling, and limits. Since an output schema exists, return value details are not needed. Complete for the tool's complexity.

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?

Despite 0% schema description coverage, the description thoroughly explains each parameter: csv_content (full CSV text), dry_run (default true, parse only), on_conflict (skip/overwrite/error). Adds essential meaning beyond the schema.

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's function: 'Import subscribers from a CSV blob with conflict handling.' It uses a specific verb (import) and resource (subscribers), and distinguishes from sibling tools like subscriber_create (single) and subscriber_bulk_export.

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 guidance on CSV format, row limit (5000), conflict handling options, and recommends using dry_run first. However, it does not explicitly contrast with alternative tools for single subscriber operations.

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