kopern_import_agent

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

Annotations indicate readOnlyHint=false and idempotentHint=false, which align with the description stating it creates a new agent. The description adds 'No LLM cost' but omits details like whether the import overwrites existing agents, validation behavior, or error handling. Adequate but not rich.

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?

Two sentences, no filler. The first clearly states the action and input, the second lists created components and a notable benefit. Every sentence adds value.

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 single-parameter tool with high schema coverage, the description covers the basics but lacks information on prerequisites (e.g., valid JSON), error scenarios, and how it differs from creating an agent manually. Given the many sibling tools, more contextual guidance would improve completeness.

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 coverage is 100% with the single 'data' parameter described as 'The full Kopern agent export JSON (from kopern_export_agent)'. The description reinforces this with 'Import an agent from a Kopern export JSON', but adds no extra structural or format details beyond the schema.

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 specifies the action ('Import an agent'), the input format ('Kopern export JSON'), and the outcome ('Creates a new agent with all skills, tools, extensions, and grading suites'). This distinguishes it from sibling tools like 'kopern_create_agent' (likely from scratch) and 'kopern_export_agent' (export).

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, such as 'kopern_create_agent' or when an import is appropriate. The only hint is 'No LLM cost', but no when-not-to-use or alternative naming is provided.

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