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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List' implies a read operation, but it does not disclose pagination behavior, ordering, filtering, statuses, or what fields are returned for each import. Behavioral transparency is minimal.

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, front-loaded sentence with no filler or redundant wording. It is appropriately concise for a list operation, though slightly more context could have been added 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 straightforward paginated list tool, the schema covers the parameters and the description states the core intent, so it is minimally viable. However, with no annotations and no output schema, an agent is left without information about return shape, import statuses, ordering, or how this tool fits with the other contact 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?

The input schema fully documents all three parameters with clear descriptions, including the required organization_id, limit with a maximum of 100, and cursor for pagination. The description adds no parameter-level meaning, but the 100% schema coverage sets the baseline at 3.

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 clear action with a specific resource: 'List contact imports'. The plural 'imports' helps differentiate it from singular operations like commsharbor_contact_import_get, though it does not specify scope, filtering, or relationship to related import tools.

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?

Usage is implied: this is the tool for listing contact imports. However, there is no explicit guidance about when to prefer this over related tools such as contact_import_get, contact_import_errors, or contact_import_preview, nor any discussion of alternatives.

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