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. It only says 'List', which implies a read operation, but it fails to mention pagination (despite the cursor parameter), response format, or any other operational behavior. The description does not contradict annotations (there are none), but it is dangerously underinformative.

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, concise sentence that front-loads the action and resource without any filler. Every word earns its place, and it is appropriately sized for a list operation with minimal complexity.

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?

Even for a simple list tool, the description is incomplete. It does not explain that results are paginated via the cursor, nor does it describe the output shape. Since there is no output schema, the agent has no guidance on what to expect in the response, making the description insufficiently complete for a tool with pagination.

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 already provides complete descriptions for all three parameters (organization_id, limit, cursor) with 100% coverage. The description adds no new meaning—'of the organization' merely echoes the schema's organization_id description. Thus, the schema does the heavy lifting, and the description contributes nothing extra.

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 (List) and the resource (contact imports) with an explicit scope (organization). It differentiates from sibling tools like commsharbor_contact_import_get by being plural and implying a collection listing, making it immediately distinguishable.

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 a clear use case: list all contact imports for the organization. However, it does not explicitly state when to avoid this tool or mention alternatives such as commsharbor_contact_import_get for retrieving a single import, leaving the choice largely implicit.

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