list_app_templates

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

No annotations are provided, so the description carries the behavioral burden. It discloses that this is a listing operation returning id/name/coordinates and what kind of templates are included, but it does not explicitly state read-only safety, pagination, ordering, or any filtering limits. For a simple zero-parameter list this is adequate but not rich.

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 short and front-loaded: it first states what is listed, then gives the deployment alternative, then clarifies the template scope. Every sentence adds useful selection or invocation context without waste.

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 a zero-parameter, no-annotation, no-output-schema list tool, the description supplies enough context to select and call it correctly. It identifies the resource, the returned fields, the intended follow-up tool, and the scope distinction; only minor operational details like ordering or pagination are absent.

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, so there is no parameter semantics to clarify. The description does not need to compensate for schema gaps, and the empty schema is unambiguous.

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 a specific verb and resource ('List the app template store') and clarifies exactly what the listed items are ('deployable starter apps (id/name/coordinates)'). It also explicitly distinguishes these from per-service presets and points to the sibling action tool, so an agent can identify this as the read-only catalog lister without opening another schema.

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 clearly directs the agent to use `deploy_template` when it wants to deploy one of the templates, which is the key alternative action. It also gives scope guidance by clarifying that these are full app templates rather than per-service presets, though it does not enumerate other list tools for comparison.

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