bulk_create_a_custom_deal_field_value

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

Annotations include idempotentHint=false and destructiveHint=false; the description explicitly states 'Not idempotent' and 'Creates data', adding value beyond annotations. It also includes a warning label ('🟡 WRITE · creates data'). No contradictions.

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?

The description is concise, using three lines: an emoji/label line, a one-line description, and a caution sentence. It is front-loaded and contains no filler.

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 a nested input schema and no output schema. The description clarifies idempotency and write nature, but does not mention return values, error behavior, or success criteria. Gaps exist for a 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 the schema already fully documents parameters. The description adds no additional parameter details, resulting in baseline score of 3.

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 'Bulk create a custom deal field value' and 'Creates a new record', identifying the action (bulk create) and resource (custom deal field value). The sibling set includes a singular create tool, distinguishing this as the bulk version.

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?

The description provides a usage caution: 'Not idempotent — calling twice may create duplicates.' However, it does not explicitly state when to use this tool versus alternatives like the singular create_custom_deal_field_value.

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