Get Contact Import

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

Annotations only declare readOnlyHint: true, so the description adds value by revealing that contact imports are asynchronous and can be in queued, in_progress, completed, or failed states. This is useful behavioral context beyond the read-only safety hint, though it doesn't describe return format or error handling.

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 two concise sentences, front-loading the core purpose and immediately providing workflow context. There is no wasted wording.

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 read tool with one parameter, a read-only annotation, and no output schema, the description covers the purpose, usage context, and expected statuses sufficiently. It provides complete guidance for an agent to invoke it correctly.

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 schema fully describes the single 'id' parameter with the description 'Contact import ID' (100% coverage). The description does not add any further parameter semantics, so the baseline of 3 applies.

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 retrieves the status and counts of a contact import by ID, using a specific verb and resource. It distinguishes itself from siblings like create-contact-import and list-contact-imports by focusing on a single import's status.

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 gives explicit guidance to use this tool after create-contact-import to track progress, naming the allowed statuses. It provides clear context but does not mention when not to use it or suggest alternatives like list-contact-imports for viewing all imports.

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