import_connection

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Import/create' implies mutation, but it does not state whether the operation is idempotent, what side effects occur, whether it requires specific permissions, or what the response looks like. No information about error conditions or existing connections is provided.

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, focused sentence that front-loads the action and resource. It is appropriately concise with no fluff. However, it is under-specified, which is a completeness issue rather than a structure issue, so the conciseness itself is well-handled.

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 mutation tool with no annotations, no output schema, and zero parameter coverage, the description is severely incomplete. It fails to explain the environment parameter, the payload requirements, the expected outcome, or any constraints. The agent has insufficient information to correctly invoke this tool without external documentation.

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 0%, and the description does not explain either parameter. It only mentions 'payload shape' without specifying the structure or required fields, and it does not clarify how 'environment' is used. With no schema descriptions, the description must compensate but fails to provide any parameter-level meaning.

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 states a clear verb ('Import/create') and resource ('a connection') and adds a specific detail about the payload shape ('using the Nango API payload shape'). It is distinct from sibling tools like list_connections or get_connection, though it could be confused with create_connect_session since both create/import connections. The purpose is clear but not fully differentiated.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context (e.g., requires an environment), or scenarios where this is preferred over create_connect_session or other connection-related tools. The agent is left to infer usage from the name and siblings.

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