kopern_deploy_template

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

Annotations indicate this is a mutation (readOnlyHint: false). The description adds that it creates agent, skills, tools, and grading suite 'in one shot', which is useful behavioral context beyond the annotations. No contradiction.

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?

Three concise sentences: first states action and scope, second specifies what is created, third provides a usage hint. No superfluous information.

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 tool's complexity (creating multiple components), the description provides sufficient context for an agent to understand its role in the workflow. However, it lacks details on return values or error states, slightly reducing completeness. With no output schema, the agent must infer the return from the description.

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 the schema already describes both parameters well. The description primarily echoes the schema's parameter descriptions ('Template slug (from kopern_list_templates)', 'Onboarding answers'). It adds no new semantic depth beyond what the schema provides, resulting in a baseline score of 3.

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 uses the specific verb 'Deploy' with the resource 'agent from a template', clearly distinguishing it from siblings like kopern_create_agent which likely creates from scratch. It also quantifies the templates (28 general + 9 vertical), adding precision.

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 explicitly tells the agent to use kopern_list_templates to see available slugs, establishing a clear prerequisite. However, it does not explicitly state when not to use this tool (e.g., if you need to customize an existing agent).

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