prompt_list

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states the action of listing and does not describe return format, pagination, sorting, or any side effects. The category filter is not mentioned in the description, leaving behavioral details undisclosed.

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 that immediately conveys the tool's purpose. It contains no redundant information and is well front-loaded.

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 tool with one optional parameter and no output schema, the description is minimally adequate. It states the core function but does not mention the optional category filtering or what the returned list contains. Given the complexity is low, the description is not severely incomplete, but could be more helpful.

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 provides full coverage of the category parameter with an enum, default value, and description. The tool description adds no additional parameter semantics, and the schema already explains the parameter fully, so a baseline score of 3 is appropriate.

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 'List all available AI prompt templates' uses a specific verb (List) and clearly identifies the resource (AI prompt templates), with 'all' indicating scope. This distinguishes it from sibling tools like prompt_get and prompt_generate, which imply retrieving or generating individual prompts.

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 implies usage for listing templates but does not explicitly state when to use this tool instead of alternatives like prompt_get or prompt_generate. There is no mention of exclusions or alternative tool suggestions, so guidance is only implied by the action verb.

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