bulk_create_offers

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

Without annotations, description discloses the preview-then-confirm safety pattern. But lacks details on error handling, rate limits, or destructive potential. Adds some value beyond schema but not comprehensive.

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 sentences efficiently cover purpose and usage. No wasted words; front-loaded with essential information.

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?

Adequately explains core workflow for a 5-param tool with no output schema or annotations. Missing details on CSV format, max rows, error handling, but schema fills some gaps. Could be more thorough.

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 covers 80% parameters with descriptions. Description adds context ('Each row becomes one offer' for csv_text, 'previews payloads first' for confirmed) but not substantial beyond schema. Baseline 3 is appropriate.

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?

Clearly states 'Bulk-create ExD offer items from CSV rows. Each row becomes one offer.' The verb and resource are specific, and it differentiates from sibling tools like single offer creation or metadata fieldgroups.

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 clear guidance: use dry_run to preview, set confirmed true to execute. Implicitly advises against direct execution without preview. However, does not explicitly mention when not to use or alternatives like individual creation.

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