create_contact

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It only states the action without revealing side effects, validation rules, authentication requirements, idempotency, or what happens on duplicate creates. The description is not misleading, but it adds no behavioral context beyond the name.

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 immediately states the action and subject with zero superfluous words. It is well-structured for rapid agent parsing and follows a front-loaded pattern, making it optimally concise.

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 create operation with no annotations and no output schema, the description lacks critical context such as expected return values, error handling, and duplicate-contact behavior. While the schema covers parameters, the tool's behavioral context is under-specified, leaving an agent unable to predict the outcome or handle failures.

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 fully documents all four parameters with 100% coverage, providing complete definitions for name, email, phone, and description. The description adds no additional meaning beyond what the schema already provides, so a 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 states 'Создать новый контакт в JivoSite' (Create a new contact in JivoSite), which is a specific verb-resource pair with a clear platform context. It unambiguously distinguishes the tool from read-only siblings like get_contacts and send_message by declaring a create action.

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 provides no guidance on when to use this tool versus alternatives such as get_contacts or send_message. It does not mention any prerequisites, exclusions, or scenarios where another tool would be preferred, leaving usage entirely to inference.

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