kopern_create_agent

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

Annotations indicate a write operation (readOnlyHint=false). The description adds that it creates an agent and returns an ID, but misses details like authentication requirements, idempotency (not idempotent), or potential side effects (e.g., duplicate names).

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 consists of two concise sentences that front-load the action and key details. No unnecessary information, every word earns its place.

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 the complexity (8 params, no output schema), the description covers core functionality but omits default values (e.g., model default), constraints (e.g., name uniqueness), and behavior of optional parameters like provider and builtin_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 coverage is 100%, so baseline is 3. The description summarizes 'system prompt, model, and optional skills' but does not add significant meaning beyond the schema. For instance, it doesn't explain default values or enum options.

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 'Create a new AI agent' with specific inputs (system prompt, model, optional skills) and output (returns agentId). It effectively distinguishes from sibling tools like kopern_get_agent, kopern_update_agent, and kopern_delete_agent.

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?

The description implies usage for creating agents but lacks explicit guidance on when to use it versus alternatives such as kopern_import_agent or kopern_update_agent. No when-not-to-use or context-specific advice is provided.

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