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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds value beyond that by exposing the endpoint and the status enum values (DISPATCHED, COMPLETE, FAILED) and the meaning of the counters. It omits whether results are paginated or complete, which matters for a polling-style list tool.

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?

A single dense sentence front-loads the resource, then the return fields, then the endpoint. Nothing is redundant and the status enum is packed inline rather than given its own sentence.

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 carries the burden of describing return values, and it does so by naming the key fields and status values. What remains missing is the shape of the collection itself — pagination, ordering, or whether historical tasks are included.

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 tool takes no parameters, so the baseline is 4. The description correctly implies that no filters (list id, status, date) are available, consistent with the empty schema.

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 gives a specific verb and resource ("List contact import tasks") and enumerates the fields returned, so an agent knows exactly what it retrieves. It does not differentiate itself from the sibling emailchef_get_import_task, which fetches a single task by id, so the sibling distinction is left implicit.

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?

Mentioning status, progress and counts implies the polling/monitoring use case for imports, which is reasonable implied guidance. However, it never states when to use this versus emailchef_get_import_task, nor any prerequisite (e.g., that an import must have been started via emailchef_import_contacts).

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