create_contact

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

No annotations are provided, so the description carries the transparency burden. It does disclose a validation rule ('Provide at least a name, email, or phone') and makes the write operation obvious with 'Create'. However, it omits details like return value, error behavior, or duplicate handling.

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 extremely concise: two sentences plus an example. Every sentence adds value, the purpose is front-loaded, and no information is repeated from the schema.

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?

For a simple creation tool with full schema coverage, the description is sufficiently complete. It specifies the core purpose, a key validation rule, and an illustrative example. However, it does not clarify the ambiguity between 'name' and 'first_name/last_name' fields, and with no annotations or output schema, a bit more context could be helpful.

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?

The schema already describes all 7 parameters (100% coverage), so the baseline is 3. The description adds the cross-field constraint that at least one of name, email, or phone is required, and provides a concrete example, enriching the schema's information.

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 new contact in your CRM' with a specific verb and resource. It unambiguously distinguishes this creation tool from siblings like update_contact, get_contact, and delete_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 implies when to use the tool (when creating a new contact) but does not explicitly contrast it with alternatives like update_contact or get_contact. It provides a usage requirement (at least one of name, email, or phone) but no clear exclusions.

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