list_available_templates

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the action and directory, but does not explicitly confirm the operation is read-only, mention any limitations (e.g., empty directory behavior), permissions, or side effects. The verb 'List' implies non-mutating behavior, but the description lacks explicit transparency about behavioral traits.

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 sentence that is front-loaded with the action (List) and resource (prompt templates), and adds the directory location. Every word is necessary and there is zero fluff.

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 simple list tool with no parameters and an existing output schema, the description is complete. It clearly specifies what is listed and where, and the sibling context (list_available_reports) makes the differentiation obvious without needing extra detail.

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?

This tool has zero parameters, so the baseline is 4. There are no parameter semantics to clarify beyond the schema, which is already complete (100% coverage).

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 the tool lists all available prompt templates in the prompts/ directory, using the specific verb 'List' and a precise resource. It naturally distinguishes itself from siblings like list_available_reports (reports vs. templates) and upload_and_generate_prompt (listing vs. generating).

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 description provides clear context—listing prompt templates from a specific directory—which implicitly tells the agent when to use this tool over siblings. However, it does not explicitly mention exclusions or alternatives, such as 'use list_available_reports for reports', so it falls short of a 5.

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