List Available AI Agent Templates

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

With no annotations, the description carries full burden. It details what the tool returns (name, cost, env vars, ports, resource footprint) but does not explicitly state it is read-only or has no side effects. However, it implies a safe list operation, so it is fairly transparent.

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 paragraph that front-loads the main purpose, then provides agent examples, usage context, and return details. It is informative without being verbose, and each 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?

Given no output schema, the description covers all relevant information: agent names, costs, return fields, and usage scenario. It also links to a sibling tool for deployment, making it complete for the user's needs.

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?

The tool has zero parameters and schema coverage is 100%. The description does not need to add parameter info, and it correctly omits any. The baseline for 0 parameters is 4, but the description fully satisfies the need, earning a 5.

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 lists curated AI agent templates, provides specific examples with details, and distinguishes from sibling tools like varity_agent_info and varity_deploy_agent by stating when to use it and what follow-up action to take.

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?

Explicitly says 'Use this when a developer asks what AI agents can I deploy?' and directs to deploy with varity_deploy_agent after selection, providing clear context and alternatives.

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