list_library_prompts

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

With no annotations, the description carries the full burden for behavioral disclosure. It does not mention that this is a read-only operation, nor does it disclose pagination behavior or that all prompts are returned by default. The scope is limited to the user's library, but important behavioral traits are absent.

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, clear sentence without wasted words. It is front-loaded with the action and resource. However, it is minimal and could add more context without becoming verbose.

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 moderate complexity and complete schema documentation, the description is adequately functional but lacks an output schema or behavioral notes. It does not explain return format or mention optional filters, though the schema covers parameters. It is sufficient for a simple list tool but not complete for richer use.

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?

Schema description coverage is 100%, so the baseline is 3 even without parameter details in the description. The description adds no additional meaning beyond what the schema already provides, but it does not need to compensate for gaps.

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 saved prompts from the user's Pretty Prompt library, using a specific verb and resource. It distinguishes itself from sibling tools like list_library_folders, which targets folders, and save_to_library, which is for saving.

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 no guidance on when to use this tool versus alternatives. It does not mention criteria like filtering or when to prefer list_library_folders or improve_prompt. There is no context about exclusions or prerequisites.

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