create_standard_connect_session

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

No annotations provided, so the description carries full burden. It discloses that the tool creates a session with tags but omits behavioral details such as side effects (e.g., whether existing sessions are affected), required permissions, or error states.

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, but it is under-specified. While short, it fails to convey necessary context, making it insufficiently informative for an agent to use correctly.

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 10 parameters (5 required), no output schema, and no annotations, the description must provide substantial context. It barely explains the tool's purpose and leaves agents uninformed about parameter usage, return values, and integration with other tools.

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%, requiring the description to compensate. However, the description only generically mentions tags and provides no explanation of the 10 parameters (e.g., environment, provider_config_key, principal). It adds no semantic value beyond the schema's property titles.

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 'Create a Connect session with recommended Nango tags plus optional MCP convention tags' clearly specifies the verb (create), the resource (Connect session), and distinguishes it from the sibling 'create_connect_session' by emphasizing the tagging aspect.

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 explicit guidance on when to use this tool versus alternatives like 'create_connect_session' or 'create_reconnect_session'. The description implies it's for sessions with tags but provides no when-not-to-use or prerequisite context.

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