create_contact

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

No annotations provided, so the description carries full burden. It does not disclose required permissions, side effects (e.g., uniqueness constraints on 'name'), or any behavioral traits beyond the basic creation action. The '[WRITE]' tag hints at write operation but adds little detail.

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?

Extremely concise (single line), but at the cost of missing essential details. The '[WRITE]' prefix provides some structure, but the description is too terse to be fully informative.

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?

Given 7 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, error conditions, or the expected behavior of the 'raw' parameter. Missing context for real-world usage.

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 description does not add any meaning beyond the input schema, which has 57% coverage. Parameters like 'firstName' and 'lastName' lack schema descriptions, and the tool description does not compensate. The 'raw' object is mentioned as 'Advanced' but not further explained.

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 the action 'Create a new contact,' which is a specific verb+resource. It distinguishes from siblings like 'create_invoice' and 'update_contact.' However, it lacks additional context like what type of contact (e.g., customer, supplier).

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?

No guidance on when to use this tool versus alternatives (e.g., 'update_contact' for modifications). There is no mention of prerequisites or scenarios where creation might fail.

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