List Contact Imports

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

The annotations include readOnlyHint=true, which already communicates the read-only safety. The description adds a note about optional status filtering and the purpose of discovering IDs, but it does not describe pagination behavior or return format. Given the annotation coverage, this is acceptable but not rich.

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?

Two sentences with no unnecessary words. The primary action is front-loaded ('List contact imports from Resend'), and the optional filter and use cases are succinctly stated.

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 list operation with no output schema, the description conveys purpose, filtering, and use cases. The mention of 'discover import IDs' hints at the return contents. Pagination details are covered in the schema, making the description adequately complete for selecting and invoking the tool.

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 has 100% description coverage for all four parameters, including detailed explanations for pagination and status filtering. The description only repeats 'Optionally filter by status' and adds no new semantic information beyond what the schema already provides.

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 'List contact imports from Resend' with a specific verb and resource. It distinguishes the tool from siblings like list-contacts or get-contact-import by explicitly referring to 'contact imports' and the use case of discovering import IDs.

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?

Provides explicit usage context: 'Use to discover import IDs or review past imports.' This tells when to use the tool, though it does not explicitly mention alternatives (e.g., get-contact-import) or when not to use it.

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