create_contact

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

No annotations are present, so the description must cover behavioral traits. It states that the tool creates a contact and returns JSON details, but it does not disclose potential side effects (e.g., duplication checks, authentication needs, or rate limits). The description is adequate but leaves gaps.

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 structured with Args and Returns sections, making it easy to scan. It is not overly verbose, but the parameter list repeats schema information without significant condensation. A small trim would improve conciseness.

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 6 parameters (2 required), an output schema, and no annotations, the description covers the essential inputs and output. It lacks details on error handling or edge cases, but for a straightforward create operation it is nearly complete.

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 0% description coverage, but the tool description provides explanations for all 6 parameters, including required labels. This adds meaning beyond the schema's type and title. However, it could be more precise (e.g., phone format) for a top score.

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 Crelate.' It uses a specific verb ('create') and resource ('contact'), and the tool name itself differentiates it from siblings like create_candidate or create_company.

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 the tool is for creating new contacts, but it does not provide explicit guidance on when to use this vs. alternatives (e.g., update_contact for existing contacts, or sister create tools). No exclusions or prerequisites are mentioned.

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