import_connection

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

With no annotations, the description carries full burden for behavioral disclosure but only states the basic action. No mention of idempotency, overwrite behavior, permissions, side effects, or error states (e.g., if connection already exists). This is nearly a tautology of the name.

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 sentence with no fluff, but it sacrifices completeness for brevity. It earns its place by stating purpose, but lacks detail expected for a tool with complex parameters (nested objects) and no annotations.

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?

Given no annotations, no output schema, and a complex payload object (additionalProperties: true), the description is severely incomplete. The agent lacks information about return values, error handling, and how to construct the payload correctly, making successful invocation unlikely.

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 3 parameters (environment, payload, confirmation) with 0% schema description coverage. The description only hints that the payload follows the Nango API shape, with no explanation of environment, confirmation, or valid payload structure. The agent cannot infer parameter meanings from the tool alone.

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 action (import/create) and the resource (connection) with a specific qualifier ('using the Nango API payload shape'), distinguishing it from sibling tools like 'create_connect_session' or 'set_connection_metadata'. The verb and resource are precise.

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?

No usage guidance is provided. The description does not specify when to use this tool over alternatives (e.g., 'create_connect_session' for standard flows) or any prerequisites. The agent receives no decision support.

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