Deploy an AI Agent Template

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

The description discloses that deployment makes the agent accessible at a URL and that env variables vary per agent. Since no annotations are present, it carries the full burden and adequately describes the mutation, though it lacks info on auth or error handling.

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 sentences, front-loaded with core action, no wasted words. Every sentence adds meaningful 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?

For a tool with 3 params and no output schema, the description covers purpose, usage guidance, and parameter details. It references sibling tools and setup steps, though it could mention error scenarios or default behaviors.

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%, baseline is 3. The description adds value by explaining the env parameter with example, name as URL slug, and agent as the list, going beyond 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 states it deploys a curated AI agent from 5 templates and provides the URL. It distinguishes itself from siblings like varity_delete_deployment by specifying when to use each.

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?

It explicitly states when to use this tool (e.g., 'deploy hermes', 'I want a Telegram bot') and advises calling varity_agent_info first to get required env vars. It also references the alternative varity_delete_deployment for stopping.

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