list_prompts

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'List all prompt templates' and does not mention pagination, filtering behavior, ordering, return format, or potential side effects. The word 'all' is potentially misleading given the page/pageSize parameters in the schema.

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, front-loaded sentence with no filler words. It efficiently communicates the core action and resource, making it easy for an agent to parse quickly.

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 the lack of annotations and output schema, the description is too thin to fully contextualize the tool. It does not clarify whether 'all' means all results or paginated pages, what fields each prompt template includes, or whether this returns a simple list or a paginated object. This is a notable gap for an agent that needs to interpret the result correctly.

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?

All 5 parameters are fully described in the input schema (100% coverage), so the description does not need to add parameter details. The description makes no reference to parameters, but the schema already provides comprehensive semantics, meeting the baseline of 3.

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 'List' and names the resource 'all prompt templates in DreamingAI', clearly distinguishing this tool from siblings like get_prompt (which retrieves a single prompt) and create_prompt/update_prompt/delete_prompt (which mutate prompts). It leaves no ambiguity about the tool's core function.

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 this tool is for listing all prompt templates, but it does not explicitly state when to use it versus alternatives, nor does it mention exclusions or filtering as an alternative. Usage context is present but not elaborated; no sibling alternatives are referenced.

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