list_templates

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates the tool returns a list of templates and their descriptions, and the verb 'List' implicitly signals a read-only operation appropriate for this query tool. However, it does not explicitly mention side-effect-freeness or other behavioral nuances.

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, concise sentence of about 8 words, front-loading the action and resource. Every word contributes meaning, with no filler or redundant 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?

The tool is simple (no parameters, no annotations) and has an output schema, so the description only needs to convey the scope and output type. 'List all available project template combinations and their descriptions' fully satisfies this requirement, making the tool adequately described.

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 input schema has zero parameters, so the baseline is 4. The description adds no parameter details because none are needed; it simply states that all templates are listed, which is consistent with the empty 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 uses the specific verb 'List' with the resource 'all available project template combinations' and includes output details ('their descriptions'), clearly stating the tool's function. It distinguishes itself from sibling tools like configure_project and create_project by focusing solely on enumeration.

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?

The phrase 'all available' implies the tool is used for discovery before project configuration or creation, but there is no explicit guidance on when to use it versus alternatives. It neither mentions exclusions nor names specific sibling tools as alternatives.

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