List sound presets

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

readOnlyHint=true already declares the safety profile, and the description adds genuinely useful behavior beyond that: what fields come back per preset and the nondeterminism/seed semantics of downstream generation. It does not say whether the entire preset catalog is returned or capped, which is the one behavioral gap.

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?

Front-loaded with the core action, then filtering, then generation semantics — a logical order with no filler. The closing seed sentence is slightly tangential to a listing tool but earns its place by preventing confusion with generate_sfx.

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 two-optional-parameter, read-only listing tool with no output schema, the description covers inputs, returned fields, and cross-tool behavior, which is nearly everything an agent needs. The only omission is result-set size/pagination expectations when no filter is supplied.

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% and already defines both parameters, including the category enum and the all-terms-must-match rule for query. The description's category list merely repeats the enum, and the query examples ("metal", "calm", "sword") illustrate intent but add little semantics beyond the schema.

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?

States a specific verb and resource ("List the procedural sound effect presets") and immediately characterizes the content (Eastern wuxia/xianxia and general game sounds) plus what each entry carries (category, tags, use case). It is clearly distinguishable from the mutating sibling generate_sfx, which it names.

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?

Gives concrete filtering paths (by category enum or a search term) and states the relationship to generate_sfx — presets are inputs to generation, each call yields a random variation, and a seed reproduces one. That is clear context for when to reach for this tool, though it never explicitly says "call this first to discover presets before generating."

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