create_a_secondary_contact

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

Annotations confirm creative, non-idempotent, non-destructive behavior. The description reinforces this with 'creates data' and adds the duplicate warning, providing behavioral context beyond 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?

The description includes repetitive phrases ('Create a secondary contact' appears twice) and a redundant header line. It could be more concise without losing 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?

The tool has nested objects and no output schema. The description provides basic purpose and a non-idempotency note but lacks prerequisites, response details, or relationship to other tools, making it only somewhat complete.

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?

Input schema has 100% coverage with descriptions for all parameters (deal and contact). The description adds no extra meaning beyond what the schema provides, meeting baseline but no more.

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 'Create a secondary contact' and 'Create a new secondary contact for a deal', with the verb 'create' and resource 'secondary contact'. It distinguishes from siblings like 'create_a_new_contact' and 'update_a_secondary_contact'.

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 notes the operation is write (creates data) and explicitly states 'Not idempotent — calling twice may create duplicates', guiding usage. However, it does not compare with other create tools or specify when to use this over alternatives.

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