sw_list_presets

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

With no annotations, the description carries the full burden. It discloses that presets are only skeletons and that group filtering controls output (omitting returns all). It also lists the valid group values. This provides useful behavioral context beyond a simple 'list'.

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 concise, with a clear sentence followed by a structured parameter section. No filler or redundant information. Each sentence adds value.

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 the tool's simplicity and the presence of an output schema, the description adequately covers the tool's purpose and parameter behavior. It also relates to sw_plan for context. It could mention the output format, but the output schema presumably covers that. Overall, it's sufficient for an agent to select and invoke the tool 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 schema only defines 'group' as an optional string with no description. The description compensates by listing the exact valid group values and explaining the default behavior (all groups when not provided). This fully clarifies the parameter's meaning and usage.

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 '列出场景预设' (list scenario presets) with a specific verb and resource. It also clarifies that presets are skeletons, distinguishing them from full scenarios handled by sw_plan. The purpose is unambiguous.

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 notes that specific parameters are determined by sw_plan, implying this tool is for exploring preset skeletons rather than building scenarios. It also explains the optional group filter and that omitting it returns all groups. However, it doesn't explicitly enumerate alternative tools or exclusion criteria.

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