unanet_create_contact

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

The description merely restates the tool name with no additional behavioral disclosure. There are no annotations, so the description should explain side effects, permissions, duplicate handling, or required fields, but it does not.

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 a single, concise sentence that is easy to parse, but it lacks any additional structure or useful detail. It is not a tautology but is minimally 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 the tool has 7 parameters, no annotations, and no output schema, the description is far too sparse. An agent cannot determine required fields, potential errors, or expected response without more information.

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 input schema has no descriptions for its seven parameters, and the description does not mention any parameter names or constraints. The agent must infer meaning from 'firstName', 'lastName', and 'email' without any added context.

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 tool's function: creating a new contact in Unanet. It uses a specific verb ('Create') and names the resource ('contact'), which distinguishes it from sibling tools like updating leads or creating opportunities.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, whether this is for new contacts only, or how it differs from update operations.

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