import_connections

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

No annotations are provided, so the description carries full burden. It doesn't disclose whether existing connections are destroyed, whether import is additive or destructive by default, whether the overwrite flag defaults to false, or any auth/validation requirements. For an import operation that writes to system state, this is a significant transparency 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 concise sentence with zero waste. It conveys the core purpose efficiently. Though it could be more informative, it doesn't suffer from padding or redundancy.

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 state-modifying import tool with no annotations and no output schema, the description is thin. It doesn't address the format of the 'connections' object, behavior defaults for overwrite, potential for partial failures, or relationship with export_connections. With nested objects and a state-writing operation, more context is warranted to be complete.

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 100%, so both parameters ('connections' and 'overwrite') are documented in the schema. The description adds no additional meaning beyond what the schema provides. The 'overwrite' boolean semantics are clear from its own description, and 'connections' is described as the configurations to import. Per the baseline rule for >80% coverage, a 3 is appropriate.

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 'Import connection configurations from backup' which identifies a specific verb (import) and resource (connection configurations). However, it doesn't clearly distinguish from sibling 'export_connections' as a counterpart or relate to 'connect_from_config'. The purpose is understandable but the scoping around what 'backup' means is vague.

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 guidance on when to use this vs alternatives like connect_from_config or list_connections. The description doesn't mention prerequisites (e.g., where the backup comes from, format expected) or which sibling tools would be alternatives for importing vs direct configuration. There's clear context that it's for restoration from backup but no explicit when-to-use or when-not-to-use guidance.

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