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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'create CRM contact,' which reveals the basic mutation but does not mention response behavior, duplicate handling, organization scoping, or consequences of the create operation.

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 highly concise and free of filler, delivering the core action in three words. It is not padded, though it could have been slightly more informative without harming clarity.

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 annotations and no output schema, the one-sentence description is thin. It does not state what the create operation returns, whether existing contacts with the same email are affected, or that organization_id is required beyond what the schema already lists. More context is needed given the many sibling CRM and import tools.

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?

Schema description coverage is 100%, so the parameters (email, company_id, first_name, organization_id) are already documented in the input schema. The description adds no additional meaning about formats, constraints, or relationships between parameters, so the baseline of 3 applies.

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 'create CRM contact' uses a specific verb and resource, clearly stating the tool's function. It distinguishes this tool from siblings like crm_contacts_update, crm_contacts_delete, and crm_contacts_list by specifying the create action on a contact.

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?

There is no guidance about when to use this tool versus alternatives such as commsharbor_contact_import_confirm for bulk imports or commsharbor_crm_contacts_update for modifying existing contacts. The description provides no exclusions, prerequisites, or context to help an agent choose correctly.

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