list-templates

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

Discloses default filtering and the effect of one parameter. Recommends a specific template ID. However, with no annotations, it does not cover rate limits, authentication needs, or edge cases like empty results.

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, no redundancy. Front-loaded with main action, then provides important defaults and recommendations.

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 simplicity (three booleans, no output schema), description covers defaults and a concrete recommendation. Could mention return format (list of template objects) but not required for agent to use tool correctly.

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. Description adds context for includeRunpodTemplates but not for the other two parameters; their schema descriptions are already clear and match the description.

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?

Description clearly states the tool lists available templates, specifies default behavior (user's own templates) and flags to expand scope. It distinguishes from sibling tools like create-template, delete-template, get-template.

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?

Provides clear guidance on when to use includeRunpodTemplates to include official templates. Lacks explicit when-not-to-use or comparisons with other list tools, but context is sufficient for correct selection.

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