list_style_presets

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

No annotations are provided, so the description carries the full burden. It clearly implies a read operation ('List') and describes the conceptual content of presets, but it does not mention return format, ordering, pagination, or whether it returns full preset objects or just names. For a zero-parameter list tool, this is adequate but not detailed.

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?

Two sentences, no filler. The first states the action, the second provides defining context. Every word earns its place.

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 output schema and no annotations, the description is mostly complete: it defines what is listed and what a style preset is. It could mention the shape of the returned data (e.g., names vs. full objects), but the description is sufficient for an AI agent to invoke it 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?

The tool has zero parameters, so the schema is empty. The description adds value by explaining what style presets are (color palettes, shape defaults, layout rules), which helps the agent infer the kind of data returned. Since there are no parameters to document, a baseline of 4 applies and the description meets it.

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 opens with a specific verb+resource: 'List all available style presets.' This clearly distinguishes the tool from siblings like apply_style_preset and lookup_style_tokens. The second sentence adds useful context about what style presets are, reinforcing purpose without ambiguity.

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 ('when you need to see all presets') but does not explicitly state when to choose this over alternatives. Sibling tools like apply_style_preset and lookup_style_tokens exist, but the description gives no guidance on when to use this tool instead. This is clear context but no exclusions or explicit 'when to use'.

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