list_styles

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

With no annotations available, the description carries the burden and discloses the key behavioral context: it returns only name/description per style and requires darktable to be running with the darktable-mcp Lua plugin installed. It doesn't detail error cases or explicitly state read-only behavior, but 'list' plus the return description makes the non-destructive nature reasonably clear.

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?

Four short sentences, each earning its place: the action, the return content, the prerequisite relationship to apply_preset, and the runtime requirement. The most important information is front-loaded and there is no filler.

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 zero-parameter listing tool with no output schema, the description covers the purpose, the returned data shape, the dependency on apply_preset, and the external runtime prerequisite. Nothing essential for invoking it correctly is missing.

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 has no parameters, so there is nothing for the description to add about parameters. The 0-parameter baseline of 4 applies; the description instead usefully explains what the output contains.

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 and resource: 'List all darktable styles (presets) installed on the user's system.' It also states the returned fields (name and description), which makes the tool's function unambiguous and distinct from sibling tools like apply_preset.

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?

It explicitly states when this tool is required: 'Required discovery step before calling apply_preset, since style names must match exactly.' This provides clear sequencing and identifies the relevant sibling, so an agent knows to call this before apply_preset and why.

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