hda_list

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

With no annotations, the description carries full burden. It discloses the read-only nature, the underlying Houdini API calls, deduplication logic, and the server-side response cap. These are meaningful behavioral traits, though it does not cover potential errors or pagination details.

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 compact and front-loaded with the core purpose first. It includes implementation details and dedup logic, but these might be more detailed than necessary for an AI agent. Still, there is minimal redundancy, and each sentence contributes information.

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?

This is a simple list tool with no output schema and no annotations. The description covers purpose, behavior, and the filter, but it does not explicitly state the return value structure (e.g., array of objects with fields). The dedup keys imply some fields, but the lack of explicit return format leaves a gap.

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 single parameter 'category' lacks any schema description (0% coverage). The description adds only '可选透传过滤' (optional pass-through filter), giving minimal semantic meaning. It clarifies that the parameter filters results but does not explain allowed values or filtering behavior in detail.

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 begins with '枚举已加载 HDA' (enumerate loaded HDAs), which is a specific verb+resource statement. It clearly identifies the tool as a listing operation for loaded HDAs, distinguishing it from sibling tools like hda_install or hda_get.

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 for listing loaded HDAs but does not explicitly state when to use this tool versus alternatives. It mentions the optional category filter but provides no exclusions or comparative guidance relative to other list-oriented sibling tools.

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