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

Despite destructiveHint=true, the description discloses the deferred pipeline mechanics: matching against existing contacts by several keys, batching into a midnight import, and committing only after a user reviews and clicks Run. It explicitly clarifies 'nothing is created in real time and no duplicates are forced', which is exactly the non-obvious behavior an agent needs and is not derivable from the annotation.

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?

Purpose and recommendation are front-loaded, then the longer clause earns its length by explaining the deferred-commit behavior. It is effectively one dense sentence followed by the endpoint path; slightly run-on but no filler.

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?

With no output schema, the description still omits what the submission returns (e.g., an import/transaction identifier). However, for a 23-param mutation tool it explains the async lifecycle thoroughly, so the main gaps are return-value and per-parameter detail rather than core behavior.

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 48% (below the 50% threshold), so the description must compensate but largely does not. It only hints that name, email, phone, address and reference are used for matching, leaving the majority of the 23 parameters (city, state, tags, custom_fields, email_type, etc.) with no added meaning.

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 a specific verb+resource ('Submit a new or updated contact through Virtuous's import pipeline') and immediately positions it as 'the recommended way to add contacts', which distinguishes it from the read/lookup siblings like find_contact and get_contact. Nothing else in the sibling set performs contact creation, and the pipeline semantics make its role unambiguous.

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?

It gives clear when-to-use context ('the recommended way to add contacts') and implies the tool handles both new and updated contacts. It stops short of naming an explicit alternative to prefer or a when-not condition, so it is strong but not fully routing guidance.

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