List Contact Imports

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

No annotations are provided, so the description carries full burden. It does not disclose whether the operation is read-only, what happens with pagination (though schema has after/before), or any potential side effects. For a list operation, read-only is implied but not stated.

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 very concise: two sentences with no unnecessary words. The first sentence front-loads the action and resource. Every word earns its place.

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 simple list tool with moderate complexity (4 params, pagination), the description covers purpose and optional filtering. However, it lacks explanation of pagination behavior (after/before) and does not describe the return structure (e.g., list of import IDs). Given no output schema, more detail would help an agent understand what to expect.

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 baseline is 3. The description adds 'Optionally filter by status' which aligns with the status enum parameter, and 'discover import IDs' hints at response purpose. However, it does not add significant meaning beyond the schema for after, before, or limit parameters.

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 tool lists contact imports from Resend, and mentions optional filtering by status. It specifies the resource (contact imports) and the action (list), but does not explicitly differentiate from sibling list tools like list-contacts. However, the resource is unique enough.

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 provides usage context: 'Use to discover import IDs or review past imports.' It implies when to use this tool but does not state when not to use it or mention alternatives (e.g., get-contact-import for a single import). No explicit exclusions.

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