designer_list_presets

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

No annotations provided, so the description carries full burden. It explains the tool lists all available presets and gives examples, but does not disclose behavioral traits like return format, pagination, or performance characteristics. For a simple list tool with no parameters, it is adequate but not thorough.

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 and resource. It includes valuable examples without wasted words. Every part serves a purpose.

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 no parameters, output schema, or annotations, the description is the sole source of information. It tells what the tool does and provides examples, but does not explain the return structure or any limits. For a simple list tool, it is moderately complete but could be improved by specifying the output format.

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?

No parameters exist, and schema description coverage is 100% (empty schema). The description adds context about the preset content beyond the schema, such as listing specific design systems. This meets the baseline expectation for a no-parameter tool.

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 verb 'List', the resource 'all available design presets', and provides context about their nature as code-ready token configurations from specific premium design systems. This distinguishes it from sibling tools like designer_get_preset and designer_list_personalities.

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?

No explicit guidance on when to use this tool versus alternatives. While it's implied that this is for getting an overview of presets, it doesn't state when not to use it or suggest other tools for specific needs. Sibling tools like designer_get_preset exist for retrieving individual presets, but this is not mentioned.

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