bulk_create_contacts

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

Without annotations, the description should disclose behavioral traits. It mentions deduplication and a size limit but omits important details like error handling, atomicity, or response format. For a bulk creation tool, this is insufficient.

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 sentences with no redundancy. Critical details are front-loaded: purpose, cost, dedup, limit.

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 description lacks information about return values, success/failure indications, and partial success behavior. Given no output schema and no annotations, the description should provide a more complete picture 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 description adds value by noting 'FREE,' 'Deduplication is enforced,' and 'Max 100,' which are not in the schema. This helps the agent understand constraints beyond the property definitions.

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 explicitly states 'Create multiple contacts at once,' clearly identifying the action (create) and resource (contacts). The bulk aspect distinguishes it from sibling tools like 'create_contact' (singular).

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 implies when to use this tool (bulk creation) but does not explicitly mention alternatives or when to avoid it. However, the presence of 'Max 100 contacts per request' sets a clear constraint.

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