create_reconnect_session

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'create a reconnect session' without explaining what that entails—whether it is idempotent, what happens to existing sessions, or any side effects. For a mutation-like tool, this is a significant gap.

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 and therefore concise, but it is under-specified rather than efficiently structured. It lacks any front-loading of key facts beyond the basic action, and there is no attempt to organize additional context (e.g., prerequisites, typical use cases). It is not verbose, but it is also not effectively structured.

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 annotations, no output schema, and no parameter explanations, the description is far from complete. The tool has several close siblings, and this description does not explain when this variant is needed. An agent has almost no context to invoke the tool correctly, making it severely deficient.

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 lists three required parameters but provides no descriptions (schema coverage is 0%). The tool description does not explain the meaning or format of 'environment', 'connection_id', or 'provider_config_key'. An agent cannot know what values to pass or how they relate to the session creation.

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 ('Create') and a specific resource ('a Nango reconnect session for an existing connection'). It is not a tautology and conveys the core action, though it does not differentiate it from sibling tools like create_connect_session or create_standard_connect_session. The word 'reconnect' gives some differentiation, but not enough to fully distinguish.

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?

There is no guidance on when to use this tool versus the similar create_connect_session or create_standard_connect_session. No preconditions, context, or exclusions are mentioned. An agent must infer usage solely from the name and minimal description, which is insufficient.

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