netease_create_playlist

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

Beyond the annotations, the description discloses important behavioral traits: it refuses an existing exact name, verifies returned ID/ownership/privacy, preserves other playlists, and never retries uncertain results automatically. This gives the agent critical safety and side-effect information that annotations alone do not provide.

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, then adds necessary prerequisites and behavioral caveats. Every sentence contributes useful information without redundancy or 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?

Despite leveraging an output schema, the description covers prerequisites, failure conditions, verification behavior, and side-effect expectations. For a create operation with two parameters, this is complete enough for an agent to invoke it correctly and anticipate outcomes.

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 has no parameter descriptions, so the description carries the burden. It adds meaning for the 'name' parameter by noting that an existing exact name is refused, and for 'isPrivate' by stating that private is the default. While it does not fully explain all boolean semantics, it compensates well for the 0% schema description coverage.

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 states a specific verb ('Create') and resource ('empty owned playlist') and clearly distinguishes this from sibling tools like netease_list_playlists, netease_delete_playlist, and netease_set_liked. It also includes key scoping details ('after user authorization', 'Private by default') that make the tool's purpose 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 gives clear invocation context: it requires user authorization and the NETEASE_ENABLE_PLAYLIST_CREATE=1 flag, making it easy to know when this tool applies. It does not explicitly name alternatives or state when not to use it, but the sibling names and the create-vs-manage operation make the selection obvious.

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