list-presets

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

No annotations exist, so the description must bear the behavioral burden. It states the tool lists presets from folders but omits details like return format (e.g., full paths vs names), behavior on invalid folders, or default directories that are searched. Minimum required disclosure for a listing tool.

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 extraneous words. It covers the core purpose efficiently, though it could benefit from a brief sentence on output or usage context without losing conciseness.

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 listing tool, the description is adequate but lacks specification of the return structure (list of strings, objects). No output schema exists, so the description should clarify what each result contains. Sibling tool 'search-presets' may have more detail, but this tool stands alone.

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 coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema, merely restating that folders can be provided. No examples or clarifications of parameter interactions are given.

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 .ffx presets from specified folders, using a specific verb (list) and resource (presets). It differentiates from sibling tools like 'search-presets' and 'apply-preset' by focusing on enumeration from directories.

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 mentions listing from 'common or provided folders' but does not specify when to use defaults vs custom paths, nor does it contrast with 'search-presets' for filtering. No explicit when-to-use or when-not-to guidance is provided.

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