zernio_create_contact

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

Annotations are absent, so the description carries full burden. It only states the action without disclosing behavioral traits such as required permissions, duplicate handling, or side effects. Agents cannot infer safety or constraints from this minimal description.

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 sentence with no fluff, achieving conciseness. However, it is overly terse given the lack of behavioral or usage guidance. Every sentence earns its place, but the description could include more context without becoming verbose.

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 mutation tool with no output schema and no annotations, the description is incomplete. It does not specify success/error behavior, required fields beyond the schema, or how it differs from similar tools. Agents lack contextual cues to use it correctly.

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 covers all three parameters with descriptions (100% coverage). The description adds no additional meaning beyond what the schema provides, such as format constraints or validation rules. Baseline score of 3 is appropriate.

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 Zernio CRM,' identifying the verb and resource. However, it does not differentiate from sibling tools like zernio_create_whatsapp_contact or zernio_bulk_create_contacts, which could lead to confusion about which tool to use for standard CRM contacts.

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, exclusions, or scenarios where a different tool (e.g., bulk or WhatsApp contact creation) would be more appropriate.

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