itglue_create_contact

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. It only mentions required fields and array structures, omitting details on permissions, uniqueness constraints, side effects, or error conditions.

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 concise at two sentences, front-loading the core action and required fields. It avoids redundancy, though it could benefit from structuring the array descriptions more clearly.

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 no output schema and limited annotations, the description lacks important context: return value (e.g., created contact ID), error handling, prerequisites, and potential side effects. With 10 parameters and low schema coverage, more detail is needed.

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 schema description coverage is 40%, and the description adds value by clarifying the structure of 'contactEmails' and 'contactPhones' arrays (e.g., typical label-name values). However, many parameters (lastName, title, notes, etc.) receive no additional meaning beyond the schema.

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 contact') and specifies the required fields ('organizationId and firstName'). It also distinguishes from 'itglue_update_contact' by implying creation rather than update, but does not elaborate on the specific resource type.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention when not to use it (e.g., bulk creation via other methods) or provide context for choosing between sibling 'create' tools.

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