list_templates

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

readOnlyHint=true already establishes this is a safe read, so the bar is lower. The description adds useful domain context by explaining what a template is, but discloses nothing about result ordering, pagination, or whether the list is scoped to the caller's account — details that matter for an enumeration call.

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 core purpose is front-loaded in a single short sentence with a clarifying gloss. The trailing 'HTTP GET /templates' is marginally useful for endpoint mapping but is largely redundant with the tool name and consumes a line.

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 no-parameter, read-only listing with annotations covering the safety profile and no output schema, the description supplies enough for an agent to call it correctly. The main residual gap is what the returned template objects contain and whether the list is paginated or complete.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly signals an unfiltered list with no arguments.

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 states a specific verb and resource ('List the templates') and the parenthetical clarifies that a template is the image/what runs inside a sandbox, which an agent would not otherwise know. It stops short of explicitly distinguishing itself from the sibling get_template, but 'List' vs. 'get_template' makes the plural/singular split reasonably inferable.

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?

Usage is only implied: an agent can infer this is for enumerating available templates, presumably before create_sandbox. There is no explicit guidance to use get_template for a single template's details, nor any note on prerequisites or when listing is unnecessary.

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